From: Bruno Wolff III <bruno@wolff.to>
To: Thomas Kellerer <shammat@gmx.net>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: Postgres 15 upgrades and template1 public schema
Date: Wed, 19 Oct 2022 17:48:28 -0500
Message-ID: <20221019224828.GA11721@wolff.to> (raw)
In-Reply-To: <54d740ed-1158-c8d4-4cae-15c06e95c9e6@gmx.net>
References: <20221019203602.GA6563@wolff.to>
<54d740ed-1158-c8d4-4cae-15c06e95c9e6@gmx.net>
On Wed, Oct 19, 2022 at 23:30:58 +0200,
Thomas Kellerer <shammat@gmx.net> wrote:
>
>Bruno Wolff III schrieb am 19.10.2022 um 22:36:
>>I noticed when I did an upgrade from Postgres 14 to 15 that the
>>public schema in template1 was still owned by postgres instead of
>>pg_database_owner. I was expecting it to change because the release
>>notes said that new database clusters would have that. But shouldn't
>>new clusters use what is set in template1?
>
>This is explained in the release notes:
>
> The change applies to new database clusters and to newly-created
> databases in existing clusters.
> Upgrading a cluster or restoring a database dump will preserve
> public's existing permissions.
How do new databases in pre-existing clusters get the new public schema
security if it doesn't come from template1?
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: bruno@wolff.to, shammat@gmx.net
Subject: Re: Postgres 15 upgrades and template1 public schema
In-Reply-To: <20221019224828.GA11721@wolff.to>
References: <20221019203602.GA6563@wolff.to> <54d740ed-1158-c8d4-4cae-15c06e95c9e6@gmx.net> <20221019224828.GA11721@wolff.to>
* 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