Horton

Re: [PATCH] improve the pg_upgrade error message

Daniel Gustafsson <daniel@yesql.se>

View thread View on postgr.es
From: Daniel Gustafsson <daniel@yesql.se>
To: Jeevan Ladhe <jeevan.ladhe@enterprisedb.com>
Cc: Suraj Kharage <suraj.kharage@enterprisedb.com>, Justin Pryzby <pryzby@telsasoft.com>, Laurenz Albe <laurenz.albe@cybertec.at>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2022-03-24T21:48:24Z
Lists: pgsql-hackers 
> On 1 Dec 2021, at 11:15, Daniel Gustafsson <daniel@yesql.se> wrote:
> 
>> On 1 Dec 2021, at 10:59, Jeevan Ladhe <jeevan.ladhe@enterprisedb.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/

Commits

  1. List offending databases in pg_upgrade datallowconn check

  2. pg_upgrade: clarify the database names in error files