Re: ALTER TABLE SET ACCESS METHOD on partitioned tables

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Justin Pryzby <pryzby(at)telsasoft(dot)com>
Cc: Soumyadeep Chakraborty <soumyadeep2007(at)gmail(dot)com>, Zhihong Yu <zyu(at)yugabyte(dot)com>, pgsql-hackers(at)postgresql(dot)org, Ashwin Agrawal <ashwinstar(at)gmail(dot)com>, vanjared(at)vmware(dot)com
Subject: Re: ALTER TABLE SET ACCESS METHOD on partitioned tables
Date: 2023-07-19 02:49:49
Message-ID: ZLdPTWk8MCiapFEy@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Jul 16, 2023 at 09:37:28PM -0500, Justin Pryzby wrote:
> I understand that it's possible for it to be conditional, but I don't
> undertand why it's desirable/important ?

Because it's cheaper on repeated commands, like no CCI necessary.

> It's not conditional in the tablespace code that this follows, nor
> others like ATExecSetStatistics(), ATExecForceNoForceRowSecurity(),
> ATExecSetCompression(), etc, some of which are recently-added. If it's
> important to do here, isn't it also important to do everywhere else ?

Good point here. I am OK to discard this point.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message mao zhang 2023-07-19 03:01:19 FATAL: operator class "xxxx" does not exist for access method "btree"
Previous Message mao zhang 2023-07-19 02:39:44 FATAL: operator class "xxxx" does not exist for access method "btree"