On 06.05.2021 08:35, Amit Langote wrote:
> On Wed, May 5, 2021 at 7:59 PM Pavel Luzanov
> <p.luzanov@postgrespro.ru> wrote:
>> 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
> That makes sense, thanks for noticing. How about the attached?
I like it.
Especially the link to the ALTER TABLE, this avoids duplication of all
the nuances of the the DETACH .. CONCURRENTLY.
--
Pavel Luzanov
Postgres Professional: https://postgrespro.com
The Russian Postgres Company