Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vpbkl-00Bwuq-1L for pgsql-bugs@arkaria.postgresql.org; Tue, 10 Feb 2026 00:37:19 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vpbkk-00DGO6-1g for pgsql-bugs@arkaria.postgresql.org; Tue, 10 Feb 2026 00:37:18 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vpbkk-00DGNy-0s for pgsql-bugs@lists.postgresql.org; Tue, 10 Feb 2026 00:37:18 +0000 Received: from fout-b5-smtp.messagingengine.com ([202.12.124.148]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1vpbki-00000001u4f-0hbw for pgsql-bugs@lists.postgresql.org; Tue, 10 Feb 2026 00:37:17 +0000 Received: from phl-compute-06.internal (phl-compute-06.internal [10.202.2.46]) by mailfout.stl.internal (Postfix) with ESMTP id E3A2F1D00049; Mon, 9 Feb 2026 19:37:14 -0500 (EST) Received: from phl-frontend-04 ([10.202.2.163]) by phl-compute-06.internal (MEProxy); Mon, 09 Feb 2026 19:37:15 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= cc:cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm3; t=1770683834; x=1770770234; bh=UJMqz7AHJP NmUKf1YaQvBs5VH/osNd1JOnxdrS/0NFw=; b=eY/9oikURyHlFK/ovP3wpfSF9F Cw57D9C5wyIUIQ3OdNARmBI60LnCFq63rJizkpHK558I/OflPtD//P58LmIy2WPy g0Xaf9ROjq6AlMyvOO0DMsrWt2niwni/wVB6eP8G5Hxzl3kohPebEqFC7HjnVrx7 aGGZ2Xc+HMDGQRNH2Hzf1+1VQ7VxiFrdsj3KRPNnsBLX+NO3u0XYW8Y39axxjBkp 4ryHrXMYdiajMjFqd70fI7k2ZcX4oOAD9jQNUFATaSZdz4wy3AyMdSc1kGYF1VR0 jDkdlyp0+05MXtBHi0eWzTUcVM1boyspsh806ljdRWODZv1R58L9xmHhMmgw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t= 1770683834; x=1770770234; bh=UJMqz7AHJPNmUKf1YaQvBs5VH/osNd1JOnx drS/0NFw=; b=S9wbcd1hOrFbnH62Q9NI9vtmoWD+HyVuKh0/ot2tqJSVc1AMEJh aiGjARHVs7UyEIT0yjKShZQw527a01oWzKeJHO1BGp7GsY4NpKOQxkZYUODA7dfC I99DnuFU3KCS+p8Vi+6IARqGES7gnB8xPEZF7PEx6aGECUZI2CVQsynAcmuBrEbj FG6VtudzuaaGTX+JP0QIQEeqp9zp22p4GYJYv8ad8ZX1cA0VqBOJLYaXmD53RWg4 /w002oTG3qkr5GgMuGOBmcfUBeGdd6LJ8n3NbyTtW/KnJJSBGUMiAXDsXZeXAx9j XRl6NrTf5gPN9FWTtglMen39oZ24RXXCTdg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefgedrtddtgdduleekvdeiucetufdoteggodetrf dotffvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfurfetoffkrfgpnffqhgenuceu rghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnegfrh hlucfvnfffucdljedtmdenucfjughrpeffhffvvefukfhfgggtuggjsehgtderredttddv necuhfhrohhmpefoihgthhgrvghlucfrrghquhhivghruceomhhitghhrggvlhesphgrqh huihgvrhdrgiihiieqnecuggftrfgrthhtvghrnhepteelieefudffhffhtdetleeggeeg fffhkeeuveetiefgudduvedutefggeeivdejnecuvehluhhsthgvrhfuihiivgeptdenuc frrghrrghmpehmrghilhhfrhhomhepmhhitghhrggvlhesphgrqhhuihgvrhdrgiihiidp nhgspghrtghpthhtohepgedpmhhouggvpehsmhhtphhouhhtpdhrtghpthhtohepughilh hiphgsrghlrghuthesghhmrghilhdrtghomhdprhgtphhtthhopehlrghurhgvnhiirdgr lhgsvgestgihsggvrhhtvggtrdgrthdprhgtphhtthhopehhuhhsvgihihhnrdgufehrse hgmhgrihhlrdgtohhmpdhrtghpthhtohepphhgshhqlhdqsghughhssehlihhsthhsrdhp ohhsthhgrhgvshhqlhdrohhrgh X-ME-Proxy: Feedback-ID: i0fe9450f:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 9 Feb 2026 19:37:13 -0500 (EST) Date: Tue, 10 Feb 2026 09:37:09 +0900 From: Michael Paquier To: Dilip Kumar Cc: Laurenz Albe , huseyin.d3r@gmail.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #19393: pg_upgrade fails with duplicate key violation when CHECK constraint named *_not_null exists Message-ID: References: <19393-6a82427485a744cf@postgresql.org> <2b3a2cd5f9b6e82fba6ac45b413291b01dd252ea.camel@cybertec.at> <61c535617992fff830961ecc09a9c20096bc1f36.camel@cybertec.at> <99c37bcd620778c743a413dc9a1dce53ae9f4c38.camel@cybertec.at> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="8/jmVWbv0XRHUVwL" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --8/jmVWbv0XRHUVwL Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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 --8/jmVWbv0XRHUVwL Content-Type: application/pgp-signature; name=signature.asc -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmmKfbUACgkQnvQgOdby QH2J3g//bfMyD00SPDL6di17UTCBwEjSFU+JAfONHLgLDuaVcH75IQ6aUdSxh2/Q VHI2+kSJLccDb39Snmow78isf9AC4cObq4T9D5NW7Nt3FPnhB5tk33zvEjdh+7sf w9bc3S0uWwB+Dnuxydhlci/SU4Q5pMreqSXA7BwfQMtGHm8zS6fEa6W8byB4+8zi JbsoYZODRMWK1XBMiAUvbnQ9NXA/o//cmydlPnAOI6fbqTcv/x3az0wKkRKQNwIW yvP8hqSZy27BGAMPaItO/3FOZIrnfOCV+Q1mCbvJMF3Spknzl0yY354tws5A3Rul WMbMWdQ/88pwiKL3driHi6Z2dttzIUrMAUuRqn3aozOBnx8VZPdDLe/YcXdobc5l tIUBFxD8ouxBN+KLO03h48UPmF1wt7EAFW+mCnMjAIjPKiQh5M0wso3tn4H99TgL 6R5gH5WWGkaRoSdBYpjfi6SoIMndUVm+9iAlLLTba9BAV4dF9X8CvllGTjcdIIW1 9RcpQnWZmA/6O9JrNwQlpFietakTqR5JXPxm4t2SDDS21Yw0I44GVVw0Jzr1GKBp rMBPllSSpBYiWLzKI0hCLlGdnUYS1VfdeJZpcXbaCsJD01BjVQaOGKVnVXM5+LH4 z058FLb2bdM8THb4Li33FJJxCEnX0HLu4QFSzzVpvX/u63ywhHQ= =QDUv -----END PGP SIGNATURE----- --8/jmVWbv0XRHUVwL--