| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | matt(dot)figg(at)internode(dot)on(dot)net |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Programmatically duplicating a schema |
| Date: | 2018-03-13 13:57:04 |
| Message-ID: | CAKFQuwaSR16WMTn+MB-eh30LmeJ9gpFU8iqztCJhffv=DCrydw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Mar 12, 2018 at 11:05 PM, <matt(dot)figg(at)internode(dot)on(dot)net> wrote:
> The reason we'd want to infer the create statements via pg_dump is, so we
> don't need to keep database migration files in sync with a 'create new
> schema' SQL script. It adds risk that they get out of sync, causing
> inconsistencies in new schemas created by the library.
>
Then don't have a "create new schema" script (aside from the very first
one) run your migrations even when creating new installations.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-03-13 13:58:31 | Re: Question on corruption (PostgreSQL 9.6.1) |
| Previous Message | Melvin Davidson | 2018-03-13 13:47:14 | Re: UPSERT on a view |