Re: ALTER TABLE SET ACCESS METHOD on partitioned tables - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: ALTER TABLE SET ACCESS METHOD on partitioned tables
Date
Msg-id ZLdPTWk8MCiapFEy@paquier.xyz
Whole thread Raw
In response to Re: ALTER TABLE SET ACCESS METHOD on partitioned tables  (Justin Pryzby <pryzby@telsasoft.com>)
List 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

Attachment

pgsql-hackers by date:

Previous
From: mao zhang
Date:
Subject: FATAL: operator class "xxxx" does not exist for access method "btree"
Next
From: mao zhang
Date:
Subject: FATAL: operator class "xxxx" does not exist for access method "btree"