Fix pg_upgrade to preserve datdba (was: Re: pg_upgrade failing for 200+ million Large Objects)

From: Jan Wieck <jan(at)wi3ck(dot)info>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Robins Tharakan <tharakan(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Fix pg_upgrade to preserve datdba (was: Re: pg_upgrade failing for 200+ million Large Objects)
Date: 2021-03-21 16:50:46
Message-ID: 0b5d506d-70d2-1506-bbdf-89e6453c0289@wi3ck.info
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

Regards, Jan

--
Jan Wieck
Principle Database Engineer
Amazon Web Services

Attachment Content-Type Size
pg_upgrade-preserve-datdba.v1.diff text/x-patch 3.6 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jan Wieck 2021-03-21 16:56:02 Re: pg_upgrade failing for 200+ million Large Objects
Previous Message Gilles Darold 2021-03-21 16:46:47 Re: [PATCH] proposal for regexp_count, regexp_instr, regexp_substr and regexp_replace