Re: Programmatically duplicating a schema - Mailing list pgsql-general

From David G. Johnston
Subject Re: Programmatically duplicating a schema
Date
Msg-id CAKFQuwaSR16WMTn+MB-eh30LmeJ9gpFU8iqztCJhffv=DCrydw@mail.gmail.com
Whole thread Raw
In response to Re: Programmatically duplicating a schema  (matt.figg@internode.on.net)
List pgsql-general
On Mon, Mar 12, 2018 at 11:05 PM, <matt.figg@internode.on.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.

pgsql-general by date:

Previous
From: Melvin Davidson
Date:
Subject: Re: UPSERT on a view
Next
From: Tom Lane
Date:
Subject: Re: Question on corruption (PostgreSQL 9.6.1)