From: | David Rowley <drowley(at)postgresql(dot)org> |
---|---|
To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | pgsql: Doc: Clarify lock levels taken during ATTACH PARTITION |
Date: | 2021-07-28 03:03:36 |
Message-ID: | E1m8Zr6-00007h-6a@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Doc: Clarify lock levels taken during ATTACH PARTITION
It wasn't all that clear which lock levels, if any, would be held on the
DEFAULT partition during an ATTACH PARTITION operation.
Also, clarify which locks will be taken if the DEFAULT partition or the
table being attached are themselves partitioned tables.
Here I'm only backpatching to v12 as before then we obtained an ACCESS
EXCLUSIVE lock on the partitioned table. It seems much less relevant to
mention which locks are taken on other tables when the partitioned table
itself is locked with an ACCESS EXCLUSIVE lock.
Author: Matthias van de Meent, David Rowley
Discussion: https://postgr.es/m/CAEze2WiTB6iwrV8W_J=fnrnZ7fowW3qu-8iQ8zCHP3FiQ6+o-A@mail.gmail.com
Backpatch-through: 12
Branch
------
REL_12_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/c590904d50cc93b12fc895041c34e1ea821e768c
Modified Files
--------------
doc/src/sgml/ddl.sgml | 28 +++++++++++++++++++++++++---
doc/src/sgml/ref/alter_table.sgml | 13 +++++++++++--
2 files changed, 36 insertions(+), 5 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2021-07-28 11:44:02 | pgsql: Use the AddFile function consistently in MSVC build scripts |
Previous Message | David Rowley | 2021-07-28 03:03:24 | pgsql: Doc: Clarify lock levels taken during ATTACH PARTITION |