Re: BUG #16514: pg_dump v12 puts CREATE SCHEMA public statement into the backup file - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #16514: pg_dump v12 puts CREATE SCHEMA public statement into the backup file
Date
Msg-id 29861.1593204298@sss.pgh.pa.us
Whole thread Raw
In response to BUG #16514: pg_dump v12 puts CREATE SCHEMA public statement into the backup file  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
PG Bug reporting form <noreply@postgresql.org> writes:
> I’m experiencing some weird behaviour of pg_dump: based on this thread
> https://www.postgresql.org/message-id/flat/20849.1541638465%40sss.pgh.pa.us#744c293b37793dea0f6e60676c3f3210
> , starting from v11 pg_dump should not include CREATE SCHEMA public
> statements to the dump. However, if I run pg_dump v12 with --schema public ,
> it still adds that line to the backup file,

Our interpretation of that is that you've deliberately selected the
schema, so it should be dumped.

> which breaks the ability to
> restore from it

That's rather an overstatement no?  You can just ignore the "already
exists" error.

            regards, tom lane



pgsql-bugs by date:

Previous
From: Jose Alcantara
Date:
Subject: Problem with pgadm4
Next
From: Daniel Gustafsson
Date:
Subject: Re: Problem with pgadm4