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: Peter Eisentraut <peter@eisentraut.org>, exclusion@gmail.com, pgsql-bugs@lists.postgresql.org

Date: 2025-07-03T17:48:14Z

Lists: pgsql-bugs

For the moment I've just gone ahead and pushed the bug fix,
with test cases that demonstrate the inconsistency in
behavior between stored and virtual generated columns.
Whether we should change that is probably a matter for
a separate thread.

			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