Re: Fix pg_upgrade to preserve datdba (was: Re: pg_upgrade failing for 200+ million Large Objects) - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Fix pg_upgrade to preserve datdba (was: Re: pg_upgrade failing for 200+ million Large Objects)
Date
Msg-id 384713.1616345832@sss.pgh.pa.us
Whole thread Raw
In response to Fix pg_upgrade to preserve datdba (was: Re: pg_upgrade failing for 200+ million Large Objects)  (Jan Wieck <jan@wi3ck.info>)
Responses Re: Fix pg_upgrade to preserve datdba  (Jan Wieck <jan@wi3ck.info>)
List pgsql-hackers
Jan Wieck <jan@wi3ck.info> writes:
> On 3/20/21 12:39 AM, Jan Wieck wrote:
>> On the way pg_upgrade also mangles the pg_database.datdba
>> (all databases are owned by postgres after an upgrade; will submit a
>> separate patch for that as I consider that a bug by itself).

> Patch attached.

Hmm, doesn't this lose all *other* database-level properties?

I think maybe what we have here is a bug in pg_restore, its
--create switch ought to be trying to update the database's
ownership.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Jan Wieck
Date:
Subject: Re: pg_upgrade failing for 200+ million Large Objects
Next
From: Jan Wieck
Date:
Subject: Re: Fix pg_upgrade to preserve datdba