From: Tom Lane <tgl@sss.pgh.pa.us>
To: tureba@gmail.com
Cc: Stephen Frost <sfrost@snowman.net>
Cc: pgsql-bugs@postgresql.org
Subject: Re: BUG #14650: pg_dump -c fails when 'public' schema doesn't exist
Date: Fri, 12 May 2017 14:22:20 -0400
Message-ID: <4692.1494613340@sss.pgh.pa.us> (raw)
In-Reply-To: <20170512181801.1795.47483@wrigleys.postgresql.org>
References: <20170512181801.1795.47483@wrigleys.postgresql.org>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-bugs>
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 exist
> LINE 1: ...::regclass AND pip.objsubid = 0 AND pip.objoid <> 'public'::...
> ^
> This seems to have started in commit 330b84d8c4
Yeah, this is not cool. Stephen?
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, tureba@gmail.com, sfrost@snowman.net
Subject: Re: BUG #14650: pg_dump -c fails when 'public' schema doesn't exist
In-Reply-To: <4692.1494613340@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox