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 1rfvEi-0038u3-6A for pgsql-hackers@arkaria.postgresql.org; Fri, 01 Mar 2024 05:15:08 +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 1rfvEg-00BH4F-0t for pgsql-hackers@arkaria.postgresql.org; Fri, 01 Mar 2024 05:15:06 +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 1rfvEf-00BH46-Nc for pgsql-hackers@lists.postgresql.org; Fri, 01 Mar 2024 05:15:06 +0000 Received: from fout3-smtp.messagingengine.com ([103.168.172.146]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rfvEd-002Ccg-5e for pgsql-hackers@postgresql.org; Fri, 01 Mar 2024 05:15:04 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailfout.nyi.internal (Postfix) with ESMTP id 49CB713800BD; Fri, 1 Mar 2024 00:15:02 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Fri, 01 Mar 2024 00:15:02 -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=fm1; t=1709270102; x=1709356502; bh=OudiNX9tsO L+fdk+4gAaQFYf9aunxnRiehj4Og2E7zA=; b=jJaTnjDM2DexUJIcwHJ8YllrLo 2Bz9YpV6DXAVu3h3o0Pi4F/2J3RrLVfMBu8IKSyIW0xK2CqIprUblzJ9DZSqJpzt gnbCc5yCXQTOK7/1RyUmAgUNzzwwnOXbF5CdjNNC8ULnp8yZco+R1Hn91cV/ljXc QhP591JXybV/QMCuB2LX0glL4xohN90mieMFcXMT9fvrGDv/hTjild25VZ2EEsTe lb7IV0mUWNj6mCq85ve2RHMdo/iZMgNkQYcw1exUzudgRxjS4m6Vwm8+UNgxDRVg 8JTp0xmdqeK5TsBIgJ45sUKf6orz63NfFIcespEZzE0OY4IfsJDQPytC5gYw== 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= fm1; t=1709270102; x=1709356502; bh=OudiNX9tsOL+fdk+4gAaQFYf9aun xnRiehj4Og2E7zA=; b=Hy1B+NdUSe1w12d+zoLxo5zePd+cCyFmnI9g45eXdoiz c9rSeb5UGWHW+eECeUVQOpG4RmntCwvFDHpfCCUmBDCFHamIfn5qaOrUs17V17k1 Jx8B92Sgxk+76okukongVK9AChm96VTfP4w3oWxcq8tXXuF2kyPhf3vcOsrfqSbL 6yMXLLV9UJbnQmplmh6s9Y7NVYy0J7epEaqfkrk/DJMdrXw15tpZvzl3nbeuYgro v26kMgpLnwJgx3FWne85cujxemlPvF4upZHLR+p8816ILpPd2S1+mlo/0NU/FBEe SORcKHlDTh/G3mtiks+1igiYS/Fk7h5Ym9pEl6Cb/Q== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrhedtgdejjecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenfg hrlhcuvffnffculdejtddmnecujfgurhepfffhvfevuffkfhggtggujgesghdtreertddt vdenucfhrhhomhepofhitghhrggvlhcurfgrqhhuihgvrhcuoehmihgthhgrvghlsehprg hquhhivghrrdighiiiqeenucggtffrrghtthgvrhhnpeetleeifedufffhhfdtteelgeeg geffhfekueevteeigfduudevudetgfegiedvjeenucevlhhushhtvghrufhiiigvpedtne curfgrrhgrmhepmhgrihhlfhhrohhmpehmihgthhgrvghlsehprghquhhivghrrdighiii X-ME-Proxy: Feedback-ID: i0fe9450f:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 1 Mar 2024 00:14:59 -0500 (EST) Date: Fri, 1 Mar 2024 14:14:47 +0900 From: Michael Paquier To: Jelte Fennema-Nio Cc: Justin Pryzby , Peter Eisentraut , Soumyadeep Chakraborty , Zhihong Yu , pgsql-hackers@postgresql.org, Ashwin Agrawal , vanjared@vmware.com Subject: Re: ALTER TABLE SET ACCESS METHOD on partitioned tables Message-ID: References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="pBMPLIAQ3qul84NV" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --pBMPLIAQ3qul84NV Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Mar 01, 2024 at 05:43:25AM +0100, Jelte Fennema-Nio wrote: > I think we should set the AM OID explicitly. Because an important > thing to consider is: What behaviour makes sense when later > default_table_access_method is changed? > I think if someone sets it explicitly on the partitioned table, they > would want the AM of the partitioned table to stay the same when > default_table_access_method is changed. Which requires storing the AM > OID afaict. Oops, I think I misread that. You just mean to always set relam when using an AM in the SET ACCESS METHOD clause. Apologies for the noise. -- Michael --pBMPLIAQ3qul84NV Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmXhZEcACgkQnvQgOdby QH1T+g/+O87g3rJWbYXOh6HkW9XeAz9/Z33uhMhEW0VxsNLHxxqI3OrfLV9twi/7 OTin1kKxyNKoU2Qc6Ow/ecOPl7jw4HP7N8p6Dl0Fho2r5207fCYnFSbUAQHFjuOo Jbuqrc22lzwJpZcNuyNP08rZhcRcuMeTS2tIBRYqtNHydWg4EnU5EdewO4PT4/m2 QQzAcWxaqblgExASeC7nvppbpmIGaHfzoPCk95tr6AGHzaePhdTSDQcSHoTADiiA 767xrhC/uWMJElCjidryhGnMI1lqSL6Bob/SLv/EmHYgyefHQOCLKsOjPY3w2qV5 kxT12OoDplrkWwnkDFE6Kn3t1tGp1ALVksd/0o5EotowgaZzgMFmEqol2wP+gvcG uK65ZBQOwIDiCufssGYPBM0GuSEVAfKMWtIPsKXqPu4EDKS/yeWI4DJPUhM9n7z0 SY7v1bMMRZLSHh7Ldb6vmN+2Td8E1dlUM89GldiARqzwlz7vnBEPf3eUqSIIfB7t oN4DfbVHg9rASpTbl7NiMS4btgONmjTCLLKB3vzzS0zswSOxYMTTnTNi4PY2qTOU 1fiaM5u/KqaOCgrpnBfVH33jD5diIKLUi3MBujVvhXvlqfMwJzF8MeX7wql6ftCA Jae5yyrC9TA2+tkjHoGgtqLYwTLgNFClCWjzVxCw+X+AmfG1M4I= =bgJJ -----END PGP SIGNATURE----- --pBMPLIAQ3qul84NV--