| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Alexander Lakhin <exclusion(at)gmail(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, 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-04-17 07:40:02 |
| Message-ID: | 202404170740.dv4jwhwvdieb@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2024-Apr-17, Michael Paquier wrote:
> 2) We could limit these extra ALTER TABLE commands to be generated for
> partitioned tables. This is kind of confusing as resulting dumps
> would mix SET commands for default_table_access_method that would
> affect tables with physical storage, while partitioned tables would
> have their own extra ALTER TABLE commands.
Hmm, cannot we simply add a USING clause to the CREATE TABLE command for
partitioned tables? That would override the
default_table_access_method, so it should give the correct result, no?
--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2024-04-17 07:50:02 | Re: ALTER TABLE SET ACCESS METHOD on partitioned tables |
| Previous Message | Sharique Muhammed | 2024-04-17 07:34:18 | hash_destroy on the hash table allocated with TopMemoryContext |