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

From Melvin Davidson
Subject Re: Postgresql upgrade to 9.5.12/10.3 changes pg_dump format forcloning schemas
Date
Msg-id CANu8Fix7LiJdiLrBmdGZyfuuD+HV=tRj3-D+8Gb-AVK0Cs3GWw@mail.gmail.com
Whole thread Raw
In response to Re: Postgresql upgrade to 9.5.12/10.3 changes pg_dump format forcloning schemas  (Melvin Davidson <melvin6925@gmail.com>)
List pgsql-general

On Tue, Mar 13, 2018 at 1:47 PM, Melvin Davidson <melvin6925@gmail.com> wrote:



Thank you Melvin, I forgot to mention I've already found your script before I asked here, but I didn’t think it was robust enough (please don't offend :-). Particularly, it didn't work well on PostgreSQL 10.


Aldrin,

I apologize. I just tested and found that the reason it is failing is because, once again, the catalogs have been changed. In this case the structure of sequences.
I am trying to find a workaround. I will get back to you when I do.


--
Melvin Davidson
Maj. Database & Exploration Specialist

Universe Exploration Command – UXC

Employment by invitation only!

Aldrin,

I've solved the problem with the sequences.

The attached clone_schema_10.sql has been tested on my system and now works.
Let me know if you find any bugs. As you also said it is not robust enough, Please also let me know what additional features you think it needs.


--
Melvin Davidson
Maj. Database & Exploration Specialist

Universe Exploration Command – UXC

Employment by invitation only!
Attachment

pgsql-general by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: query_to_xml() returns invalid XML when query returns no rows
Next
From: Joe Conway
Date:
Subject: Re: Reindex doesn't eliminate bloat