| From: | Fujii Masao <fujii(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: Fix ALTER DOMAIN VALIDATE CONSTRAINT locking |
| Date: | 2026-06-18 01:22:46 |
| Message-ID: | E1wa1Sw-000nIm-29@gemulon.postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Fix ALTER DOMAIN VALIDATE CONSTRAINT locking
Commit 16a0039dc0d1 reduced the lock level for ALTER DOMAIN ...
VALIDATE CONSTRAINT from ShareLock to ShareUpdateExclusiveLock.
However, that change was unsafe. If DML on tables using the domain had
already started and initialized domain constraint checks before a NOT
VALID constraint was added, it could still insert or update rows that
violated the new constraint.
This commit reverts commit 16a0039dc0d1 so that ALTER DOMAIN ...
VALIDATE CONSTRAINT once again acquires ShareLock on relations using
the domain. Also add an isolation test covering this case.
Author: Chao Li <lic(at)highgo(dot)com>
Reviewed-by: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Reviewed-by: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
Discussion: https://postgr.es/m/463C0E1A-4A40-4BCA-839C-9236B80D65EE@gmail.com
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/64797ad97d6e0a476f809979df99e0013c1933b1
Modified Files
--------------
src/backend/commands/typecmds.c | 24 +++++------------
.../isolation/expected/alter-domain-validate.out | 23 +++++++++++++++++
src/test/isolation/isolation_schedule | 1 +
.../isolation/specs/alter-domain-validate.spec | 30 ++++++++++++++++++++++
4 files changed, 61 insertions(+), 17 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2026-06-18 01:34:44 | pgsql: doc PG 19 relnotes: remove VALIDATE CONSTRAINT lock item |
| Previous Message | Bruce Momjian | 2026-06-17 23:33:55 | pgsql: doc PG 19 relnotes: mention pg_dump{all} & standard_conforming_s |