diff options
| author | David Rowley <drowley@postgresql.org> | 2021-07-28 15:02:12 +1200 |
|---|---|---|
| committer | David Rowley <drowley@postgresql.org> | 2021-07-28 15:02:12 +1200 |
| commit | 5a8a9be08307a1c06fbed4510667de6b4f40fe56 (patch) | |
| tree | 973dd471caf1bc3367408cbe3d02a0f61a441521 /src/tutorial/basics.source | |
| parent | ad3b40eb26a30d376e8448eb1170421501f0fc6b (diff) | |
| download | postgresql-5a8a9be08307a1c06fbed4510667de6b4f40fe56.tar.gz postgresql-5a8a9be08307a1c06fbed4510667de6b4f40fe56.zip | |
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
Diffstat (limited to 'src/tutorial/basics.source')
0 files changed, 0 insertions, 0 deletions