Re: BUG #16243: non super user take pg_restore found some errors.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: 270246512(at)qq(dot)com
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #16243: non super user take pg_restore found some errors.
Date: 2020-02-04 16:27:38
Message-ID: 7310.1580833658@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> When take the pg restore, both backup action and restore use non-super role
> user “cm” which is the owner of the DB. During pg_restore, the log show some
> errors such as "could not execute query: ERROR: must be owner of extension
> plpgsql", "could not execute query: ERROR: must be owner of extension
> plpgsql". I have some confusion. Are they correct behavior? If not, how to
> avoid them? thanks in advance.

This is expected behavior in v10. In later versions (I forget if
this was changed in v11 or v12), we rearranged the duties of pg_dump
so that it won't try to drop and recreate the plpgsql extension.
That wasn't an entirely backwards-compatible change though, so
it wasn't back-patched.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Andres Freund 2020-02-04 16:29:01 Re: BUG #16241: Degraded hash join performance
Previous Message Tom Lane 2020-02-04 16:00:29 Re: BUG #16241: Degraded hash join performance