From: | "Igal (at) Lucee(dot)org" <igal(at)lucee(dot)org> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Multiple Schemas vs. Multiple Databases |
Date: | 2017-10-13 20:24:46 |
Message-ID: | b8ddca1f-d3d7-f1cf-e226-43286829fa96@lucee.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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 <http://lucee.org/>
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Kellerer | 2017-10-13 21:36:51 | Re: Multiple Schemas vs. Multiple Databases |
Previous Message | John R Pierce | 2017-10-13 19:47:44 | Re: Multiple Schemas vs. Multiple Databases |