From: Daniel Gustafsson <dgustafsson@postgresql.org>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Find invalid databases during upgrade check stage
Date: Wed, 06 Nov 2024 14:45:55 +0000
Message-ID: <E1t8hIA-000Tc0-PT@gemulon.postgresql.org> (raw)
Find invalid databases during upgrade check stage
Before continuing with the check start by checking that all databases
allow connections to avoid a hard fail without proper error reporting.
Inspired by a larger patch by Thomas Krennwallner.
Discussion: https://postgr.es/m/f9315bf0-e03e-4490-9f0d-5b6f7a6d9908@postsubmeta.net
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/f638aafd1ea8505750ca9546e0e0b2e4cf31027d
Modified Files
--------------
src/bin/pg_upgrade/check.c | 37 +++++++++++++++++++++-------------
src/bin/pg_upgrade/t/002_pg_upgrade.pl | 2 +-
2 files changed, 24 insertions(+), 15 deletions(-)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: dgustafsson@postgresql.org, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Find invalid databases during upgrade check stage
In-Reply-To: <E1t8hIA-000Tc0-PT@gemulon.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox