Re: BUG #18625: user-created extensions change ownership to "postgres" after upgrade

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: evgeni(at)golov(dot)de
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18625: user-created extensions change ownership to "postgres" after upgrade
Date: 2024-09-20 14:16:32
Message-ID: 2422972.1726841792@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 upgrading 15 to 16 (but also observed the same on 12 to 13), an
> extension that was previously created by a "normal" user is now owned by
> "postgres":

Yeah, this is a known shortcoming --- pg_dump doesn't make any effort
to preserve ownership of extensions. Nobody's really been motivated
to do something about that.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Evgeni Golov 2024-09-20 15:02:12 Re: BUG #18625: user-created extensions change ownership to "postgres" after upgrade
Previous Message PG Bug reporting form 2024-09-20 13:02:15 BUG #18626: Using ampersand (&) in password fails installation.