Re: BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: jian he <jian.universality@gmail.com>
Cc: exclusion@gmail.com, pgsql-bugs@lists.postgresql.org
Date: 2025-06-29T17:32:40Z
Lists: pgsql-bugs
Attachments
- fix-bug-18970.patch (text/x-diff) patch
I wrote: > jian he <jian.universality@gmail.com> writes: >> we can change to >> if (relid != tab->relid) >> LockRelationOid(relid, AccessExclusiveLock); >> obviously, the comments need to be updated. > Yeah, I came to the same conclusion after studying it for awhile. Here's a patch for that. Working on back-patching it ... regards, tom lane
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Obtain required table lock during cross-table constraint updates.
- c15798cf94c4 16.10 landed
- bbfcbc4cde4a 17.6 landed
- 8319e5cb5493 18.0 landed
- 614ffb26d1cd 15.14 landed
- 25cab4473525 14.19 landed
- 13f1e9f26a11 13.22 landed
-
Add assertions that we hold some relevant lock during relation open.
- b04aeb0a053e 12.0 cited