On Wed, Oct 19, 2022 at 19:59:52 -0400,
Tom Lane wrote:
The release notes could probably use some tweaking here. It looks to
me like pg_dumpall (and hence pg_upgrade) will adjust the ownership and
permissions of template1's public schema to match what was in the old
installation, but it doesn
On Wed, Oct 19, 2022 at 19:59:52 -0400,
Tom Lane wrote:
The release notes could probably use some tweaking here. It looks to
me like pg_dumpall (and hence pg_upgrade) will adjust the ownership and
permissions of template1's public schema to match what was in the old
installation, but it doesn
Bruno Wolff III writes:
> On Wed, Oct 19, 2022 at 23:30:58 +0200,
> Thomas Kellerer wrote:
>> 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 wi
On Wed, Oct 19, 2022 at 23:30:58 +0200,
Thomas Kellerer 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 beca
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
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
