| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Sam Darwin <samuel(dot)d(dot)darwin(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #18383: creation of public schema is not consistent |
| Date: | 2024-03-08 07:31:44 |
| Message-ID: | d7c13f4f77baeab19056c04ed6a45adcfe18585b.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hayato Kuroda (Fujitsu) | 2024-03-08 07:35:16 | RE: Re:RE: Re:BUG #18369: logical decoding core on AssertTXNLsnOrder() |
| Previous Message | PG Bug reporting form | 2024-03-08 06:00:16 | BUG #18384: It's not bug just question about documentation |