model-writtenrun 855 - may be wrong, links go to the source messages. Commit-by-commit LLM analysis is in the Commits dialog.
- Ayush Tiwari reported that SET EXPRESSION could leave existing rows violating whole-row CHECK constraints because the dependency scan only found column-specific references, and proposed rebuilding every CHECK constraint with stored and virtual regression tests in #1.
- Jian he took over implementation in #2, replacing the blanket rebuild with targeted expression inspection, adding whole-row index rebuilding, and initially rejecting changes involving whole-row policy references.
- Ayush reviewed naming, diagnostics, dead code, and locking in #3, while Zsolt Parragi identified a stored-column declaration accidentally used in the virtual test in #4; Jian incorporated corrections and further cleanup in #5 and #7, with Ayush reporting passing tests in #6.
- Ayush argued in #8 that policies are evaluated at query time and need neither rebuilding nor restrictions when a generation expression changes; Jian removed policy handling in #9, and Ayush accepted that resolution in #10.
- Solai v reproduced the original failure and verified the fix in #11; Zsolt then requested an error instead of a warning for unexpectedly null constraint expressions in #12, which Jian implemented with editorial updates in #13.
- Chao Li presented a competing approach in #14 that reused pg_depend scanning where possible and scanned pg_index for partial indexes, but the eventual commit retained Jian’s direct CHECK and index scans.
- Peter Eisentraut committed #13 as 9530898940 with helper relocation, unused-parameter removal, attribute-access cleanup, and editorial changes, announcing completion in #15.
- Nathan Bossart asked whether the open item could be marked fixed in #16, and Peter characterized the committed fix as addressing new PostgreSQL 19 functionality in #17.
- The specific SET EXPRESSION fix remained committed, but Matthias van de Meent argued in #18 that broader whole-row dependency tracking and catalog-scan costs remained unresolved, pointing to a separate proposal for explicit whole-row dependency tracking.