Re: [GENERAL] Multiple Schemas vs. Multiple Databases - Mailing list pgsql-general

From Igal @ Lucee.org
Subject Re: [GENERAL] Multiple Schemas vs. Multiple Databases
Date
Msg-id b8ddca1f-d3d7-f1cf-e226-43286829fa96@lucee.org
Whole thread Raw
In response to Re: [GENERAL] Multiple Schemas vs. Multiple Databases  (John R Pierce <pierce@hogranch.com>)
List pgsql-general
On 10/13/2017 12:47 PM, John R Pierce wrote:
On 10/13/2017 12:29 PM, Igal @ Lucee.org wrote:

The main things that I need to do is:

  a) Be able to backup/restore each "part" separately.  Looks like pg_dump allows that for schemas via the --schema=schema argument.

  b) Be able to query aggregates from the secondary "part" and store the results in the primary one, which also seems easier with multiple schemas than multiple databases.

Am I right to think that two schemas are better in this use case or am I missing something important?


generally, yeah, unless you eventually decide to split off the two databases onto separate servers for performance reasons.   Of course, to access the 'other' database, you'd need to use postgres_fdw or dblink.

Thank you both for confirming,


Igal Sapir
Lucee Core Developer
Lucee.org

pgsql-general by date:

Previous
From: John R Pierce
Date:
Subject: Re: [GENERAL] Multiple Schemas vs. Multiple Databases
Next
From: Thomas Kellerer
Date:
Subject: Re: [GENERAL] Multiple Schemas vs. Multiple Databases