Re: BUG #19393: pg_upgrade fails with duplicate key violation when CHECK constraint named *_not_null exists

On Mon, Feb 23, 2026 at 05:47:46PM +0100, Alvaro Herrera wrote:
> On 2026-Feb-22, Michael Paquier wrote:
>> 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/aYp9tTWjUqS1ffAd@paquier.xyz
> which was on Feb 10th, which is before the 18.2 release, so you couldn't
> have been considering the 18.3 release yet.

Well, you are not counting the week of the 18.2 release, this thread
being an item I had on my stack of items to look at once the tags were
applied.  It didn't make to the top of the list.  It does not matter
much at the end.  Thanks for fixing the issue!
--
Michael