Re: BUG #14650: pg_dump -c fails when 'public' schema doesn't exist

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: tureba(at)gmail(dot)com
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14650: pg_dump -c fails when 'public' schema doesn't exist
Date: 2017-05-12 18:22:20
Message-ID: 4692.1494613340@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

tureba(at)gmail(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Jeremy Cowgar 2017-05-12 18:25:23 Re: BUG #14649: Function Namespace Resolution Bug
Previous Message tureba 2017-05-12 18:18:01 BUG #14650: pg_dump -c fails when 'public' schema doesn't exist