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 1rVwyW-002J8x-8d for pgsql-hackers@arkaria.postgresql.org; Fri, 02 Feb 2024 17:05:12 +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 1rVwyT-00EcPO-1Q for pgsql-hackers@arkaria.postgresql.org; Fri, 02 Feb 2024 17:05:09 +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 1rVwyS-00EcNa-L6 for pgsql-hackers@lists.postgresql.org; Fri, 02 Feb 2024 17:05:08 +0000 Received: from mail-ej1-x62e.google.com ([2a00:1450:4864:20::62e]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rVwyL-004jxI-UE for pgsql-hackers@postgresql.org; Fri, 02 Feb 2024 17:05:07 +0000 Received: by mail-ej1-x62e.google.com with SMTP id a640c23a62f3a-a3122b70439so320390866b.3 for ; Fri, 02 Feb 2024 09:05:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1706893500; x=1707498300; darn=postgresql.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=szvgWrAudCe4FkE/RLD5cNBS7b0nPdFm0fqFtfaYuqI=; b=KuehAhgDuaUaZqOzntSQM/88kTu4BNyeeJ3YJqlPH6tK8dpco4OgUJf7doLp91AYgT KcIj5IgMMRcpNS0v5F8tLSf4BAAhYf2fvopfu1Ypvy4KsjQMIOcuTCVCNyohoAAmCloi qIGWWDsPhU/lewgV7GOc3FMxTEVC8VnHzKEqn7dGVQJS8o//DdrcPUPRRe8P3ByZhpCs qZ/w6Q3LmFmITn/NYGkTCEIelhjJjg7ZDD56xvTpQSvAGIXFb+dpG8LNz2fQxB6pXyuL vg3GApNGee2fnkmuR0tF6YiRTFkGi8FoPQE6ByHrdEdz+g6kRg+L/2DilZ6wKBdqzmVe y57w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1706893500; x=1707498300; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=szvgWrAudCe4FkE/RLD5cNBS7b0nPdFm0fqFtfaYuqI=; b=fv1uUH7z4eEGUsr+rWDg4fxikMOffpwHcf8i1ZquXSzb/HVC4+vDYriNjJ4UnOQTDg hJLCR80pKIIdNFMRUNcDKzOM+Ss7xyU8IO46c3Yv4iZQK7NvBC32mGXRor2gaRIt8dN6 eQbITlnu+PtEI0uTyBe+wetok9v8H1RD8UqKhZ6el6VPToOZSE+AMbx5/44jPfzKoed9 sxdi+yOVeQaByO4x4CmYStIxuXmDoM+0jqrcnUClD8DMFgTJqDr56Sq8PnOjaBak3SnD NxeWiu0qvPDQ9k4ZHvTMmLFI81erOw7PgGYyeEcq8c5y8p8zFu1ZPeRCbZOczlSdX+oq QXyw== X-Gm-Message-State: AOJu0YzKbKnvJNn5hLD+cQrmuhSkBqbiGeJTljp2hbdYZO7FcT2tjQm1 sOhYKVjmXIHnx9ChYYpwgIe8tq3YPqmzhMbyoYFfMchqgT5b6zPeiJNqmM+rPDT3a9LQEZnQOhj VvfJOC/1F/TuUblzTE49XJ8RtWO4= X-Google-Smtp-Source: AGHT+IHuUr6nnWzFo51TQoQfN9coTMl6iC1GvRpApPFdUDwYF/rFI5ovety8/MyeKx/hsaDLymsCS5OTo8mpsAFtMrk= X-Received: by 2002:a17:906:6d51:b0:a36:bc3:3c8b with SMTP id a17-20020a1709066d5100b00a360bc33c8bmr5906844ejt.65.1706893499566; Fri, 02 Feb 2024 09:04:59 -0800 (PST) MIME-Version: 1.0 References: <202402011550.sfszd46247zi@alvherre.pgsql> In-Reply-To: <202402011550.sfszd46247zi@alvherre.pgsql> From: Robert Haas Date: Fri, 2 Feb 2024 12:04:47 -0500 Message-ID: Subject: Re: ALTER TABLE SET ACCESS METHOD on partitioned tables To: Alvaro Herrera Cc: Justin Pryzby , Michael Paquier , Soumyadeep Chakraborty , Zhihong Yu , pgsql-hackers@postgresql.org, Ashwin Agrawal , vanjared@vmware.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Thu, Feb 1, 2024 at 10:51=E2=80=AFAM Alvaro Herrera wrote: > I think this works similarly but not identically to tablespace defaults, > and the difference could be confusing. You seem to have made it so that > the partitioned table _always_ have a table AM, so the partitions can > always inherit from it. I think it would be more sensible to _allow_ > partitioned tables to have one, but not mandatory; if they don't have > it, then a partition created from it would use default_table_access_metho= d. I agree that we don't want this feature to invent any new behavior. If it's clearly and fully parallel to what we do for tablespaces, then I think it's probably OK, but anything less than that would be a cause for concern for me. --=20 Robert Haas EDB: http://www.enterprisedb.com