Re: Teach pg_upgrade to deal with invalid databases - Mailing list pgsql-hackers

From Nathan Bossart
Subject Re: Teach pg_upgrade to deal with invalid databases
Date
Msg-id ar_aBTKVbZ-duSbT@nathan
Whole thread
In response to Re: Teach pg_upgrade to deal with invalid databases  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
List pgsql-hackers
On Thu, Sep 24, 2026 at 08:37:00AM -0700, Bharath Rupireddy wrote:
> I implemented the above approach, pg_upgrade skipping them without any
> option and emitting info about the skipped ones. I ensured the CI is
> happy. Please find the attached v2 patch.

Thanks.  IMHO we shouldn't bother adding a note to pg_upgrade's
documentation, or even emitting warnings when pg_upgrade skips invalid
databases.  For all intents and purposes, the database is already dropped
(for some definition of "dropped"), and there's nothing actionable for the
user.

-- 
nathan



pgsql-hackers by date:

Previous
From: Manu
Date:
Subject: Re: Partial indexes on system catalogs
Next
From: Nathan Bossart
Date:
Subject: Re: Report relation extension blockers within parallel lock groups