| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, 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: | 2024-02-21 07:46:48 |
| Message-ID: | cab23590-19d4-4895-9333-1c25f4194741@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2024-02-21 07:53:57 | Re: logical decoding and replication of sequences, take 2 |
| Previous Message | Michael Paquier | 2024-02-21 07:46:00 | Re: Injection points: some tools to wait and wake |