Re: Postgresql upgrade to 9.5.12/10.3 changes pg_dump format forcloning schemas - Mailing list pgsql-general

From David G. Johnston
Subject Re: Postgresql upgrade to 9.5.12/10.3 changes pg_dump format forcloning schemas
Date
Msg-id CAKFQuwZVY81PXsZJBCir7HLax_wkfBpmmACku_znwcmA7Lon9g@mail.gmail.com
Whole thread Raw
In response to Postgresql upgrade to 9.5.12/10.3 changes pg_dump format for cloningschemas  (Aldrin Martoq Ahumada <aldrin.martoq@gmail.com>)
List pgsql-general
On Fri, Mar 9, 2018 at 6:26 AM, Aldrin Martoq Ahumada <aldrin.martoq@gmail.com> wrote:
Thinking in the long term, how could be the best way to clone a schema into another?

Depends on why you are cloning schemas.

Generally not cloning is the best bet - instead place the reference schema into version control and simply install it whenever necessary.  Parameterize the installation script.

​Or, clone into a different database and leave the namespace the same.

pg_dump, as currently written, is tasked with recreating the original database exactly and safely.  If you need it to do something different you could teach it the desired behavior and add some relevant command line switches to enable said behavior.

David J.

pgsql-general by date:

Previous
From: Aldrin Martoq Ahumada
Date:
Subject: Postgresql upgrade to 9.5.12/10.3 changes pg_dump format for cloningschemas
Next
From: Herwin Weststrate
Date:
Subject: Feature request: min/max for macaddr type