From: Tom Lane <tgl@sss.pgh.pa.us>
To: evgeni@golov.de
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18625: user-created extensions change ownership to "postgres" after upgrade
Date: Fri, 20 Sep 2024 10:16:32 -0400
Message-ID: <2422972.1726841792@sss.pgh.pa.us> (raw)
In-Reply-To: <18625-77d1e2609972c616@postgresql.org>
References: <18625-77d1e2609972c616@postgresql.org>
PG Bug reporting form <noreply@postgresql.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, evgeni@golov.de, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18625: user-created extensions change ownership to "postgres" after upgrade
In-Reply-To: <2422972.1726841792@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox