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 1rchJg-001XYJ-0H for pgsql-hackers@arkaria.postgresql.org; Wed, 21 Feb 2024 07:46:56 +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 1rchJe-003Sgm-HZ for pgsql-hackers@arkaria.postgresql.org; Wed, 21 Feb 2024 07:46:55 +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 1rchJe-003Sgd-8R for pgsql-hackers@lists.postgresql.org; Wed, 21 Feb 2024 07:46:54 +0000 Received: from fout6-smtp.messagingengine.com ([103.168.172.149]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rchJb-000EPy-3K for pgsql-hackers@postgresql.org; Wed, 21 Feb 2024 07:46:53 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailfout.nyi.internal (Postfix) with ESMTP id 090D8138005F; Wed, 21 Feb 2024 02:46:51 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Wed, 21 Feb 2024 02:46:51 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eisentraut.org; h=cc:cc:content-transfer-encoding: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=1708501611; x=1708588011; bh=b4a/DaHWHtjgILh84j+IL+CEU1y/moxo Pl5oGAGUA6Y=; b=Y/t11WMngldLIb/lnZUmsM9Y86YxN1LkqjQuRf5i2KyrjbM2 y840dBPdTSg9GZ7D4h5B5RzYWrr4i3ZIhCec6Wb2NvdRVnY9yKrcdV1MQdbLvlKz iCbnZ40ph5CMIQWqKZW6vETmHhobfdyxxD9o3obVzvmqACCr3pbFeNopFAMI834J V2JNG0KuN0ONaYV87hXK8pdoBY+yfU5WDDEYUlo6/1LpLwWoNdAyKnVkh4q8gjRU Ic3yrBo9Eck0xvhELE5JQFovpaT6BOlt+7hm3b6OEDS91PHGLgbjhntxMInYXU/q 5hOVTVonbHp2EoNHrSDBg39Ms7yBI0VtTw+Q8A== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :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=1708501611; x= 1708588011; bh=b4a/DaHWHtjgILh84j+IL+CEU1y/moxoPl5oGAGUA6Y=; b=f el3MvoTxHnNvGKk3C4qLzwgJ/5njzc9h/8OYauPx8sS8wGiKJA3mRePVo6D5VwYX y4kj/2CzoFUdjBjRftnD8wraZ+HTUfKSEilnXALLXRojJ7084lWinnckgccA/dd/ CSQGKdo0cOPLge+6y+YfnDTLYb7Z2gPHbJegOY8bSJYvll9TOY35WDLskQW+VEqi yioD3JljOep3ubqJC2CQBIHsFfbTlCBKE75AAcsVI6svML5tEHsqSatwvTIBBLVx s6qYmUXjMaNs4xL9JOrG0/QP76b0GpQC28Y4D+ddX1XJAf47VKB0TYknIT/xR2uA QopeVx2NwzQJeV8VUXMYQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrfedugdduuddvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvvehfhfgjtgfgsehtjeertddtvdejnecuhfhrohhmpefrvght vghrucfgihhsvghnthhrrghuthcuoehpvghtvghrsegvihhsvghnthhrrghuthdrohhrgh eqnecuggftrfgrthhtvghrnhepgfejtdfhkeeftdeugfeileehteeljeeghfeuledthfeu tedvffdukeefjefhgeehnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrg hilhhfrhhomhepphgvthgvrhesvghishgvnhhtrhgruhhtrdhorhhg X-ME-Proxy: Feedback-ID: ie0a040ee:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 21 Feb 2024 02:46:49 -0500 (EST) Message-ID: Date: Wed, 21 Feb 2024 08:46:48 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: ALTER TABLE SET ACCESS METHOD on partitioned tables Content-Language: en-US To: Michael Paquier Cc: Justin Pryzby , Soumyadeep Chakraborty , Zhihong Yu , pgsql-hackers@postgresql.org, Ashwin Agrawal , vanjared@vmware.com References: From: Peter Eisentraut In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 21.02.24 07:40, Michael Paquier wrote: > This means that all partitioned tables would have pg_class.relam set, > and that relam would never be 0: > - The USING clause takes priority over default_table_access_method. > - If no USING clause, default_table_access_method is the AM used > > Any partitions created from this partitioned table would inherit the > AM set, ignoring default_table_access_method. > > Alvaro has made a very good point a couple of days ago at [1] where we > should try to make the behavior stick closer to tablespaces, where it > could be possible to set relam to 0 for a partitioned table, where a > partition would inherit the AM set in the GUC when a USING clause is > not defined (if USING specifies the AM, we'd just use it). Yes, I think most people agreed that that would be the preferred behavior.