Horton

Re: [PATCH] improve the pg_upgrade error message

Jeevan Ladhe <jeevan.ladhe@enterprisedb.com>

View thread View on postgr.es
From: Jeevan Ladhe <jeevan.ladhe@enterprisedb.com>
To: Daniel Gustafsson <daniel@yesql.se>
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: 2021-12-02T06:58:08Z
Lists: pgsql-hackers 
On Wed, Dec 1, 2021 at 3:45 PM 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.
>

Great! Thank you.


> --
> 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