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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Dilip Kumar <dilipbalaut(at)gmail(dot)com>
Cc: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, huseyin(dot)d3r(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19393: pg_upgrade fails with duplicate key violation when CHECK constraint named *_not_null exists
Date: 2026-02-10 00:37:09
Message-ID: aYp9tTWjUqS1ffAd@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On Fri, Feb 06, 2026 at 04:16:08PM +0530, Dilip Kumar wrote:
> Right I see, I was talking about the similar case something like[1]
> but I see it already handles the conflict and generates a conflicting
> name if a constraint with the name already exists. So we are good,
> thanks.

I had this patch marked on my tablets for a lookup, with the hope that
it would have been possible to get something done for this week's
release, unfortunately I got drifted away and lacked time. I'll look
into what you have here.
--
Michael

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Fujii Masao 2026-02-10 01:23:02 Re: basic_archive lost archive_directory
Previous Message Michael Paquier 2026-02-10 00:34:35 Re: BUG #19396: Standby and DR site replication broken with PANIC: WAL contains references to invalid pages messge

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2026-02-10 00:39:33 Re: Problems with get_actual_variable_range's VISITED_PAGES_LIMIT
Previous Message Michael Paquier 2026-02-10 00:09:57 Re: local custom injection points do not work as expected