Re: Fix pg_upgrade to preserve datdba - Mailing list pgsql-hackers

From Jan Wieck
Subject Re: Fix pg_upgrade to preserve datdba
Date
Msg-id 2284b71d-af55-2625-f8c2-cedf1f1a70ca@wi3ck.info
Whole thread Raw
In response to Re: Fix pg_upgrade to preserve datdba (was: Re: pg_upgrade failing for 200+ million Large Objects)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Fix pg_upgrade to preserve datdba  (Jan Wieck <jan@wi3ck.info>)
List pgsql-hackers
On 3/21/21 12:57 PM, Tom Lane wrote:
> 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.

Possibly. I didn't look into that route.


Regards, Jan

-- 
Jan Wieck
Principle Database Engineer
Amazon Web Services



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Fix pg_upgrade to preserve datdba (was: Re: pg_upgrade failing for 200+ million Large Objects)
Next
From: Peter Geoghegan
Date:
Subject: Re: New IndexAM API controlling index vacuum strategies