From: | John R Pierce <pierce(at)hogranch(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: database redesign |
Date: | 2013-11-08 20:09:38 |
Message-ID: | 527D4502.7080104@hogranch.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 11/8/2013 11:44 AM, zach cruise wrote:
> my response hasn't shown up on
> http://postgresql.1045698.n5.nabble.com/upgrading-to-9-3-td5777291.html so
> trying again. sorry if both show up.
>
> anyway, on database reorganization - is it recommended to group all
> sequences and domains under one public schema? or is a sequence tied
> to a table as its counter?
>
I would keep sequences in the same schema as the related table. anything
else is chaotic. if a domain is used by all the schemas, then putting
it in public makes sense, otherwise, if its just used by one schema, it
should logically be part of that schema.
> what are some replication choices for x64 systems since slony is not
> an option?
the built in streaming replication is the usual first choice.
--
john r pierce 37N 122W
somewhere on the middle of the left coast
From | Date | Subject | |
---|---|---|---|
Next Message | Sergey Konoplev | 2013-11-08 20:24:34 | Re: database redesign |
Previous Message | zach cruise | 2013-11-08 19:44:15 | database redesign |