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.94.2) (envelope-from ) id 1rSWdE-00EHFg-LL for pgsql-bugs@arkaria.postgresql.org; Wed, 24 Jan 2024 06:21:05 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rSWdD-002S7g-4X for pgsql-bugs@arkaria.postgresql.org; Wed, 24 Jan 2024 06:21:03 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rSWdC-002S7Y-SK for pgsql-bugs@lists.postgresql.org; Wed, 24 Jan 2024 06:21:02 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rSWdA-003591-9D for pgsql-bugs@lists.postgresql.org; Wed, 24 Jan 2024 06:21:01 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 6F89E5C00C3; Wed, 24 Jan 2024 01:20:59 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Wed, 24 Jan 2024 01:20:59 -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=1706077259; x=1706163659; bh=I7tuBM4aDr Aor9xmXhdk1r45IiWN2wOJ46634/Og1dU=; b=gAKzwg7L49aFvFoEwKYuWnygRF 0O70dKSYCXrq+yUuSrso8flX8DryW0Iel2VfI16f8MrVy7RrXizz7OV0owyF3amn Dzdg4ecOirkMrXdx/fkH93eVUL46TJT165EoUBNY/WvBv2ZLfJYNrzIEvzxgm5ah WQEftuDetSQSrx8CwZqUG0U3wZ1qe2O2aIbX6cDG8taibUY/webW+rOfbbl7bO4G Nb909M82HhOpGkTo+uDDqImeMQz3wkaxOs1DdWAiIEAkC/Zn6/uT+g6PRorr0wH0 8x7bg6lZ+m8XPJfPiP+AQRPCnx/df1Jl8SaZnIpHfLlQWBTe+/aBQtzBwlog== 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-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; t=1706077259; x=1706163659; bh=I7tuBM4aDrAor9xmXhdk1r45IiWN 2wOJ46634/Og1dU=; b=pDhYZjc1O2ytzbtE1qpO2YTJOp4Vy4iNEgdQWrtcH2XN PwttOsGtj8xW6r7K21nujO6fVEpcZKr/woUk9BtIb3YYjZvS0Zan687g/WI90mNm sUrF7y2iEaq7ybctFQnT6sKL8Ba4TgdhQazurVURv/D7QgUBRgsBZlbk7CzQHyXo QB3euspJBRT9sG6MAmFC3wDBeyu3QOwoDaK/P0BRJx9wxMNkr6zH1/UvMsTLz2lo mzmCdtYYoHCBL+2fWemeF7U9a6VXsTsq9/Oe0JqhYAA9aiL0Rcua8/vpyeplg7pM 6mOx35mp7/tPfOUl6AXv4xGv5z5rvB/f6Peg2B4ahg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrvdeltddgiedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne gfrhhlucfvnfffucdlfeehmdenucfjughrpeffhffvvefukfhfgggtuggjsehgtderredt tddvnecuhfhrohhmpefoihgthhgrvghlucfrrghquhhivghruceomhhitghhrggvlhesph grqhhuihgvrhdrgiihiieqnecuggftrfgrthhtvghrnhepgeffjeevgfevuddvjedtvddt ieejheduueelvddufedtgfefjedvkeevkeeivddvnecuffhomhgrihhnpehpohhsthhgrh gvshhqlhdrohhrghenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhl fhhrohhmpehmihgthhgrvghlsehprghquhhivghrrdighiii X-ME-Proxy: Feedback-ID: i0fe9450f:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 24 Jan 2024 01:20:57 -0500 (EST) Date: Wed, 24 Jan 2024 15:20:42 +0900 From: Michael Paquier To: Tender Wang Cc: Alexander Lakhin , Richard Guo , pgsql-bugs@lists.postgresql.org Subject: Re: BUG #18297: Error when adding a column to a parent table with complex inheritance Message-ID: References: <18297-b04cd83a55b51e35@postgresql.org> <38de09cc-70f3-28ee-fe67-ae13cba23e61@gmail.com> <9481c16e-8477-eb73-4e20-91bb1a13e2e0@gmail.com> <2f37c3f3-4701-5efd-c007-2b1cc310a93a@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="krhbU2kGLgDGG2cC" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --krhbU2kGLgDGG2cC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jan 23, 2024 at 11:19:57AM +0800, Tender Wang wrote: > Your reported two issues have different code path, and duplicates do not > processed. >=20 > I am considering whether there is a unified way of handling this, otherwi= se > each one will have to be dealt with separately. Yes, I don't agree with what you have posted on [1], inventing a new way to handle what is basically a way to remove duplicated ObjectAddresses, and that's what we use in the DropRole() path. The problem reported on this thread has now been fixed as of bb812ab0917e, so why not moving the rest to a different thread with a proper subject? This will attract a better audience for the topic dealt with. [1]: https://www.postgresql.org/message-id/CAHewXN=3DdPJDvaoME0G9vyemUmY-Tp= DuqQfcHJRWfUvSWX1p=3DrQ@mail.gmail.com -- Michael --krhbU2kGLgDGG2cC Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmWwrDoACgkQnvQgOdby QH3zjg//fN2bfDZk60TfXsQyLnwnbktkeQf50LhPRxBpWk8ZyG1QRV8Pj54s7ZQ3 jzHxhymP1OHvurSk+cUK8Z0yqPJ5On4LhD5xZOQR9pLKdRQTUKrIe+GQQTxtRJDu OQfxiMJTlRXMTjHO4Qlhzt6auAPwtfgNcn8EEM+az1F+L6G0mTGHMGjrzxJdrGaV Sl+Wo+nI3I/M9e45moEQY9Lv3uK31W+bRSu3CEuic9uLlowb1hw1cokRSywaBBrV SFZHFXRhCoFXERZShn6mq6vAeihduyWutloI6MR+cyncQVncYAs6GCF3xz6tkg5U /lRd7akQGuC+IRPespisQkCgBe66S3D3A1bpKMoMQpTuRTfd9lBqPIRvp5LUUkhK ELwNKGhbhqN65bjSTCT4mHd6fl5bcepFGIWsilmQYJNLo4QyWZvPn6F/aR4Jl4Bs vnTTBe83SwVDeWla74aUYWGLZJHfb5uk8dukzjln5G32OjX6Stt6IjXPdE0Ng+Pz nuv7zc/ggRj9c3CzQPyQA8Rtk1B+QC3yJquf7XGcBNtUQx6zCfYLELrftD0IScyd /eMrsYn3miAomxACtWgwDsQdy2QZtECOkKA1U3IrGQYkQB9OY+iCSO0k1ZK8my15 J5vwzgKvoiq8rtXo+tgt+wHmiJxVGjRBcH4Qurn4by1wCSoS3yw= =e57A -----END PGP SIGNATURE----- --krhbU2kGLgDGG2cC--