Re: BUG #18383: creation of public schema is not consistent - Mailing list pgsql-bugs

From Laurenz Albe
Subject Re: BUG #18383: creation of public schema is not consistent
Date
Msg-id d7c13f4f77baeab19056c04ed6a45adcfe18585b.camel@cybertec.at
Whole thread Raw
In response to Re: BUG #18383: creation of public schema is not consistent  (Sam Darwin <samuel.d.darwin@gmail.com>)
List pgsql-bugs
On Thu, 2024-03-07 at 18:48 -0700, Sam Darwin wrote:
> pg_restore: error: could not execute query: ERROR:  must be owner of schema public
> Command was: COMMENT ON SCHEMA public IS '';
>
> Well, maybe, consider if terse error messages could be more verbose.

As long as you know that restoring a dump executes SQL statements, what
is missing?  You get the statement that was executed and the error
message.  Right, you have to know what the owner of an object is, but
you cannot expect the error message to discourse on that.

Restoring a dump when you are not a superuser is always difficult.

Yours,
Laurenz Albe



pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #18384: It's not bug just question about documentation
Next
From: "Hayato Kuroda (Fujitsu)"
Date:
Subject: RE: Re:RE: Re:BUG #18369: logical decoding core on AssertTXNLsnOrder()