public inbox for [email protected]  

help / color / mirror / Atom feed

From: Álvaro Herrera <[email protected]>
To: Michael Paquier <[email protected]>
Cc: Laurenz Albe <[email protected]>
Cc: [email protected]
Cc: [email protected]
Subject: Re: BUG #19393: pg_upgrade fails with duplicate key violation when CHECK constraint named *_not_null exists
Date: Mon, 23 Feb 2026 17:47:46 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On 2026-Feb-22, Michael Paquier wrote:

> While I get the feeling of urgency, I am wondering if this particular
> fix should have been delayed and pushed for next May's release.  We
> are already doing one quick release for the regressions found in the
> CVE fixes..

I debated that with myself before pushing.  I thought the risk of
introducing a new bug or problem was pretty low; whereas the bug was
clearly already affecting real-world users in their attempts to migrate
to 18 from earlier versions, so the damage was real.

> Based on my read of the fix, I feel rather safe that this is OK.  But
> as I have quoted upthread, the reason why I did not reply yet was to
> wait for next week's release to be out before acting.  That's your
> code of course, so no objections from here, just a slight doubt about
> the timing.

Hmm, what?  The only response from you that I see in this thread is
https://postgr.es/m/[email protected]
which was on Feb 10th, which is before the 18.2 release, so you couldn't
have been considering the 18.3 release yet.

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/
"On the other flipper, one wrong move and we're Fatal Exceptions"
(T.U.X.: Term Unit X  - http://www.thelinuxreview.com/TUX/)

reply

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: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: BUG #19393: pg_upgrade fails with duplicate key violation when CHECK constraint named *_not_null exists
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox