From: Tom Lane <tgl@sss.pgh.pa.us>
To: tureba@gmail.com
cc: Stephen Frost <sfrost@snowman.net>, pgsql-bugs@postgresql.org
Subject: Re: BUG #14650: pg_dump -c fails when 'public' schema doesn't exist
In-reply-to: <20170512181801.1795.47483@wrigleys.postgresql.org>
References: <20170512181801.1795.47483@wrigleys.postgresql.org>
Comments: In-reply-to tureba@gmail.com
	message dated "Fri, 12 May 2017 18:18:01 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4691.1494613340.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Fri, 12 May 2017 14:22:20 -0400
Message-ID: <4692.1494613340@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-bugs-owner@postgresql.org

tureba@gmail.com writes:
> It seems that pg_dump -c fails when the database doesn't have a 'public'
> schema. When using a clean database, then dropping (or renaming) the
> 'public' schema, a subsequent pg_dump -c tells me:

> $ pg_dump -c test
> pg_dump: [archiver (db)] query failed: ERROR:  schema "public" does not e=
xist
> LINE 1: ...::regclass AND pip.objsubid =3D 0 AND pip.objoid <> 'public'::=
...
>                                                              ^

> This seems to have started in commit 330b84d8c4

Yeah, this is not cool.  Stephen?

			regards, tom lane


--=20
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs