Re: Adding a stored generated column without long-lived locks
Alberto Piai <alberto.piai@gmail.com>
From: Alberto Piai <alberto.piai@gmail.com>
To: Alberto Piai <alberto.piai@gmail.com>, Laurenz Albe <laurenz.albe@cybertec.at>, pgsql-hackers@postgresql.org
Cc: Álvaro Herrera <alvherre@kurilemu.de>
Date: 2026-07-03T06:42:18Z
Lists: pgsql-hackers
Attachments
v5 had a rather brittle test that was relying on a DEBUG message being emitted when phase 3 verifies or rewrites a table (via client_min_messages). That was failing on the CI because the output depends on any other setting that might affect logging (in this case it was log_statement). The attached v6 replaces it with an injection_point test. If adding new injection points to detect scans/rewrites is considered too much, I can back it out and set/reset log_statement too. But I do prefer the injection_point test. If the new injection point is good, there are also a couple more tests which might be updated to use it. Regards, Alberto -- Alberto Piai Sensational AG Zürich, Switzerland
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Improve handling of inherited GENERATED expressions.
- 8bf6ec3ba3a4 16.0 cited