model-writtenrun 171 - may be wrong, links go to the source messages. Commit-by-commit LLM analysis is in the Commits dialog.
- The documentation report in #1 identified an omitted PostgreSQL 18 compatibility change: RESTRICT foreign-key failures now return SQLSTATE 23001 instead of 23503, potentially breaking application error handling.
- Bruce Momjian asked how error-code changes should be identified for release notes in #2; Laurenz Albe recommended migration incompatibilities and clearer commit messages in #3, while Daniel Gustafsson advocated adding upgrade notes during development in #4.
- Bruce clarified the unresolved discovery problem in #5, and Kacper Kuras argued in #6 that this specific omission belonged in the PostgreSQL 18 notes, explaining that the change reused an existing error code and therefore left errcodes.txt unchanged.
- David Rowley supported documenting error-code changes because ordinary application testing can miss broken error handling, and suggested commit-message tags or guidance to improve discovery in #7.
- Kacper submitted #8 against REL_18_STABLE, placing the SQLSTATE explanation in Constraints and correcting a duplicated word; he acknowledged the alternative migration-section placement.
- Bruce committed #8 as 9412c35035, preserving its text and typo fix while moving the new entry to incompatibilities, then announced the application and reiterated the discovery concern in #9.
- With the documentation fix landed, Kacper described a prototype script for finding SQLSTATE changes in #10, reported additional PostgreSQL 19 omissions, explained the script's limitations, and offered to share it; systematic detection remained unresolved.