Re: [PATCH] improve the pg_upgrade error message

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Jeevan Ladhe <jeevan(dot)ladhe(at)enterprisedb(dot)com>
Cc: Suraj Kharage <suraj(dot)kharage(at)enterprisedb(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [PATCH] improve the pg_upgrade error message
Date: 2022-03-24 21:48:24
Message-ID: 122541F6-EAA6-4805-BDAC-D1EDA67EFCF8@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 1 Dec 2021, at 11:15, Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
>
>> On 1 Dec 2021, at 10:59, Jeevan Ladhe <jeevan(dot)ladhe(at)enterprisedb(dot)com> wrote:
>
>> Was wondering if we had any barriers to getting this committed.
>
> No barrier other than available time to, I will try to get to it shortly.

The "shortly" aspect wasn't really fulfilled, but I got around to taking
another look at this today and pushed it now with a few small changes to
reflect how pg_upgrade has changed.

--
Daniel Gustafsson https://vmware.com/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2022-03-24 21:52:45 Re: logical decoding and replication of sequences
Previous Message Tom Lane 2022-03-24 21:44:31 Re: New Object Access Type hooks