| From: | Pavel Luzanov <p(dot)luzanov(at)postgrespro(dot)ru> |
|---|---|
| To: | Amit Langote <amitlangote09(at)gmail(dot)com>, Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: ALTER TABLE .. DETACH PARTITION CONCURRENTLY |
| Date: | 2021-05-05 10:58:59 |
| Message-ID: | 0688e7c3-8bc8-a3e4-9d8e-3bcbbf3e1f4d@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello,
I found this in the documentation, section '5.11.3. Partitioning Using
Inheritance'[1]:
"Some operations require a stronger lock when using declarative
partitioning than when using table inheritance. For example, removing a
partition from a partitioned table requires taking an ACCESS EXCLUSIVE
lock on the parent table, whereas a SHARE UPDATE EXCLUSIVE lock is
enough in the case of regular inheritance."
This point is no longer valid with some restrictions. If the table has a
default partition, then removing a partition still requires taking an
ACCESS EXCLUSIVE lock.
May be make sense to add some details about DETACH CONCURRENTLY to the
section '5.11.2.2. Partition Maintenance' and completely remove this point?
1.
https://www.postgresql.org/docs/devel/ddl-partitioning.html#DDL-PARTITIONING-USING-INHERITANCE
Pavel Luzanov
Postgres Professional: https://postgrespro.com
The Russian Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dilip Kumar | 2021-05-05 11:09:16 | Re: Small issues with CREATE TABLE COMPRESSION |
| Previous Message | Craig Ringer | 2021-05-05 10:33:27 | RFC: Detailed reorder buffer stats dumps |