Re: pg_dump/pg_restore fail for TAR_DUMP and CUSTOM_DUMP from v94/v95/v96 to v11/master.

2019-03-01 Thread Tom Lane
Suraj Kharage writes: > The Commit 5955d934194c3888f30318209ade71b53d29777f has changed the logic > to avoid dumping creation and comment commands for the public schema. Yup. > As reported by Prabhat, if we try to restore the custom/tar dump taken from > v10 and earlier versions, we get the repo

Re: pg_dump/pg_restore fail for TAR_DUMP and CUSTOM_DUMP from v94/v95/v96 to v11/master.

2019-03-01 Thread Suraj Kharage
Hi, The Commit 5955d934194c3888f30318209ade71b53d29777f has changed the logic to avoid dumping creation and comment commands for the public schema. >From v11 onwards, we are using the DUMP_COMPONENT_ infrastructure in selectDumpableNamespace() to skip the public schema creation. As reported by Pr

pg_dump/pg_restore fail for TAR_DUMP and CUSTOM_DUMP from v94/v95/v96 to v11/master.

2019-02-27 Thread Prabhat Sahu
Hi, I got a failure in pg_dump/pg_restore as below: pg_dump/pg_restore fails with 'ERROR: schema "public" already exists' for TAR_DUMP and CUSTOM_DUMP from v94/v95/v96 to v11/master. -- Take pg_dump in v94/v95/v96: [prabhat@localhost bin]$ ./pg_dump -f /tmp/*tar_dump_PG94.tar* -Ft postgres -p 900