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 1rzWzi-004gM6-LD for pgsql-bugs@arkaria.postgresql.org; Wed, 24 Apr 2024 07:24:42 +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 1rzWzg-00CUtu-Se for pgsql-bugs@arkaria.postgresql.org; Wed, 24 Apr 2024 07:24:40 +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.94.2) (envelope-from ) id 1rzWzg-00CUtm-K9 for pgsql-bugs@lists.postgresql.org; Wed, 24 Apr 2024 07:24:40 +0000 Received: from wfout6-smtp.messagingengine.com ([64.147.123.149]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rzWzZ-002fG6-F5 for pgsql-bugs@lists.postgresql.org; Wed, 24 Apr 2024 07:24:40 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailfout.west.internal (Postfix) with ESMTP id EF69A1C000F6; Wed, 24 Apr 2024 03:24:30 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Wed, 24 Apr 2024 03:24:31 -0400 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=1713943470; x=1714029870; bh=DopSu/3xOt YK522TcbLODR+FKsZ8VQBfdljxPPvnrDE=; b=mAakekwy+AEtvZa7Gm+odSg43H tpb6fgz3S/YHFtH9k3B5TrmTLCzL0tV1wcKmvA+eih8kerc3KqEj6qVXYUPamidp NpyVYuGJyN1vxSF73XcHJDh4LVr9/sIMRRkWeG3sdVi19yTAZCndceeWZD0uindI ffXgsaoIevAjBlusXqRWipHPwbr0l/iStDxU99yFxsS9luEDhZ6NzOUovQ57A2h8 MEpPxBt2GMvj/IF1tx4v9ypjaI8/DifSWHQs0UETKYV/CyTqJO/TX5GzE3nT/qRb vhjOe10yRlDr9D4OfpF6ZOxRf3ALz/8f5LWvkKqFCvrompsdrTTGO5yAv+hg== 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=1713943470; x=1714029870; bh=DopSu/3xOtYK522TcbLODR+FKsZ8 VQBfdljxPPvnrDE=; b=CUwoSkFPxqWgBCe/bImuXtjx312JhyfgwVF94drDvlDE SKNaBS1/rhQT06tA7Ju1ZODf+uaC+1zyXmVNNkbD381cX7HGHgafAYeG/9Sw4kIu V5+J99/6ZANN8weGlkUDlL4Xn/D7ocwMpG225RElupKfVrbKtbgzk8+NoVnz7v17 HAl+CY3eZ2Tl6n+omK8zlTYpLTWuvn1beK61YESNy7NBMVQjelE1kvZ51sNtTS01 ssgPu6EphWTZGXgKu0mKXFn2ZfVzy8oMdzRZTv0TZufst/73+NhnWl3/DJ7MoVHw llfjXD9f0vqXG2v5T4AgPii0Iqcn6K4gnHSo84FwnA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrudelvddguddugecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enfghrlhcuvffnffculdefhedmnecujfgurhepfffhvfevuffkfhggtggujgesghdtreer tddtvdenucfhrhhomhepofhitghhrggvlhcurfgrqhhuihgvrhcuoehmihgthhgrvghlse hprghquhhivghrrdighiiiqeenucggtffrrghtthgvrhhnpeegffejvefgveduvdejtddv tdeijeehudeuledvudeftdfgfeejvdekveekiedvvdenucffohhmrghinhepphhoshhtgh hrvghsqhhlrdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghi lhhfrhhomhepmhhitghhrggvlhesphgrqhhuihgvrhdrgiihii X-ME-Proxy: Feedback-ID: i0fe9450f:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 24 Apr 2024 03:24:27 -0400 (EDT) Date: Wed, 24 Apr 2024 16:24:19 +0900 From: Michael Paquier To: "David G. Johnston" Cc: Kyotaro Horiguchi , "keith.fiske@crunchydata.com" , "ejberdecia@yahoo.com" , "david.rowley@2ndquadrant.com" , "amitlangote09@gmail.com" , "pgsql-bugs@lists.postgresql.org" Subject: Re: BUG #15954: Unable to alter partitioned table to set logged Message-ID: References: <1703025078.5205270.1565786782053@mail.yahoo.com> <20190821134434.GA9383@paquier.xyz> <20190822.171439.14634665.horikyota.ntt@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="kQgLqiBqGZ4VbBkb" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --kQgLqiBqGZ4VbBkb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Apr 23, 2024 at 05:33:00AM -0700, David G. Johnston wrote: > Correct, it is an outright bug that I see no reason not to just fix and > back-patch. The new feature needs its own thread so as not to have this > one see the same fate it had 5 years ago. The semantics have become much more complicated than 5 years ago because partitioned tables have gained support for more things, one being the recent addition of identity columns. While I've analyzed the whole, I have asked myself a couple of questions about what the best user-friendly behavior would be, implemented one and mentioned the rest. Anyway, a new thread has been created about this topic, so feel free to reply there: https://www.postgresql.org/message-id/ZiiyGFTBNkqcMQi_%40paquier.xyz -- Michael --kQgLqiBqGZ4VbBkb Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmYos6MACgkQnvQgOdby QH2/wRAAitz8mia7ZdiBV/SoUIkgEi9uIpuKDEVF30y7BRcOLF1vKV8CDihY08Sn MSYXmFJA+6xvRkDUK4/vTsllmEFbHlMSkHsHzRqltlHuXWrdblOYH3j+y5c/3xLU zYy5QtykcC2cTjrcaxhzKMAuo/lY7Z8wp6zwFnJcUEv2yhp6jDN4podDa4kQWmUy 2QjAXUFUI8kIfr/ZycFdUp696tWQ22SjZgUzhXzwjba02SIJYXDiyvu2qDmzICpR 6CrGfIja7/9bBm6xdxVHcEbOQUdxD3m9iu0+xeyTOUxVPOvmO42pDy2AqDBi1fGw 8zz0PtrKTRPS+bFLezhj2hjpablsDUzKG3HwUSA2xxjJFNbs6k19f/Z1LTOvsm6G rOMH8DaE3xxXHd/OtIvgosLZg8RtxjBV/35BVnCUAx/3VjqKvizIMI+FG0+0uUYx KIDh757l4ILaf4Q561I7iBTKp5Bj81Q20qiaho6Sdn+J+uhwC/RT2gn+qngjZ3qs +zNJBUAapIqt+ulQsighg3d0Rge+KgMe1TRPwSQmFcp6IbSueHwMbY6xXyjWviG8 CGjOtZ9BA+Zgxpgl4VNzEEQq+u0x5hDQANbOPgSXo7X9z9GgHljy9KPQN4hSWV81 Jfv9yxkTgECZ9IDjpQiSPcH/6rrB+MvDoR1WcopdjL82vW66aKk= =uJpY -----END PGP SIGNATURE----- --kQgLqiBqGZ4VbBkb--