Re: Teach pg_upgrade to deal with invalid databases

From: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Nathan Bossart <nathandbossart(at)gmail(dot)com>, Rithvika Devisetti <devisettirithvika(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Robert Treat <rob(at)xzilla(dot)net>
Subject: Re: Teach pg_upgrade to deal with invalid databases
Date: 2026-09-24 15:37:00
Message-ID: CALj2ACUW1CTtW9dxVrNWbiqMZNP10nRKptjRCwGq0EXJPhpcwQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On Tue, Sep 22, 2026 at 9:10 AM Bharath Rupireddy
<bharath(dot)rupireddyforpostgres(at)gmail(dot)com> wrote:
>
> Even if core drops them automatically, having pg_upgrade deal with
> them is useful on its own IMHO, since the upgrade could start before
> that happens. So, I prefer pg_upgrade skipping them without any
> option, emitting info about the skipped ones, which will not happen
> often in practice once core handles the drop.

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.

--
Bharath Rupireddy
Amazon Web Services: https://aws.amazon.com

Attachment Content-Type Size
v2-0001-Teach-pg_upgrade-to-skip-invalid-databases.patch application/x-patch 11.7 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dmitry Fomin 2026-09-24 15:40:52 Re: [PATCH v1 0/7] Wait event timing and tracing instrumentation
Previous Message Dmitry Dolgov 2026-09-24 15:34:56 Re: [PATCH] Add ALTER SYSTEM RELOAD