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

From Soumyadeep Chakraborty
Subject Re: ALTER TABLE SET ACCESS METHOD on partitioned tables
Date
Msg-id CAE-ML+_2dfVcxqxNOWooCLLLFRwaSda3_7uXXwsiXZNsh5TZyA@mail.gmail.com
Whole thread Raw
In response to Re: ALTER TABLE SET ACCESS METHOD on partitioned tables  (Justin Pryzby <pryzby@telsasoft.com>)
Responses Re: ALTER TABLE SET ACCESS METHOD on partitioned tables  (Zhihong Yu <zyu@yugabyte.com>)
List pgsql-hackers

On Wed, May 18, 2022 at 4:14 PM Justin Pryzby <pryzby@telsasoft.com> wrote:

> I didn't look closely yet, but this comment is wrong:
>
> + * Since these have no storage the tablespace can be updated with a simple                                                                                                                                                      
> + * metadata only operation to update the tablespace.                                                                                                                                                                            

Good catch. Fixed.

> It'd be convenient if AMs worked the same way (and a bit odd that they don't).
> Note that in v15, pg_dump/restore now allow --no-table-am, an exact parallel to
> --no-tablespace.

I agree that ATSET AM should behave in a similar fashion to ATSET tablespaces.
However, the way that ATSET tablespace currently behaves is not consistent with
the ONLY clause.

On a given partition root:
ALTER TABLE ONLY am_partitioned SET TABLESPACE ts;
has the same effect as:
ALTER TABLE am_partitioned SET TABLESPACE ts;

We are missing out on the feature to set the AM/tablespace throughout the
partition hierarchy, with one command.

Regards,
Soumyadeep (VMware)


Attachment

pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: PostgreSQL 15 Beta 1 release announcement draft
Next
From: Andrew Dunstan
Date:
Subject: Re: JSON Functions and Operators Docs for v15