[postgis-users] cross-database queries and choice of database configuration

[Paul Ramsey]

Because the feature he wants, separately backing up spatial and
attributes, can be easily achieved inside one database by putting the
different parts in different schemas. At the same time, it would be
common to expect to run queries that would going the spatial to the
attributes, and that would be very inefficient indeed over a
cross-database dblink or fdw connection.

Just do not store data you want to join together in different
databases, full stop.

P.

On Fri, Jun 29, 2012 at 9:10 PM, shirabez <shira at sfei.org> wrote:
> Following up on this thread from a few months ago, can you give a rationale
> for this perspective? Why is it better to go with one database? Performance?
> Simplicity? Both? Thanks,
>
> Shira
>
>
>
> Paul Ramsey-4 wrote
>>
>> On Thu, Mar 22, 2012 at 4:53 AM, Tim Pigden <tim.pigden@> wrote:
>>> Is this a practical approach for postgis type queries or do I have to put
>>> it
>>> all in one database to get good querying flexibility?
>>
>> No, bad approach. Put it all in one database, with the application
>> data in one schema and the geo data in another. Then for regular
>> backups you can just backup the application schema separately.
>>
>> P.
>> _______________________________________________
>> postgis-users mailing list
>> postgis-users at .refractions
>> http://postgis.refractions.net/mailman/listinfo/postgis-users
>>
>
>
> --
> View this message in context: http://postgis.17.n6.nabble.com/cross-database-queries-and-choice-of-database-configuration-tp4644336p4998684.html
> Sent from the PostGIS - User mailing list archive at Nabble.com.
> _______________________________________________
> postgis-users mailing list
> postgis-users at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users