model-writtenrun 9718 - may be wrong, links go to the source messages. Commit-by-commit LLM analysis is in the Commits dialog.
- Peter Geoghegan reported that calling functions “procedures” in the PostgreSQL 11 documentation could confuse users now that procedures were distinct objects, and Tom Lane agreed that the terminology needed correction #1 #2.
- When Peter Eisentraut raised the existing PROCEDURE keyword in operator and trigger syntax, Tom Lane questioned whether adding FUNCTION was worthwhile, Peter Geoghegan favored documenting the legacy usage, and Vik Fearing asked whether FUNCTION or ROUTINE would be preferable #4 #5 #6 #7.
- Peter Eisentraut submitted documentation cleanup and FUNCTION alternatives for operator, trigger, and event-trigger syntax, explaining that documentation-only changes left awkward inconsistencies; PROCEDURE remained accepted, while broad contrib cleanup and trigger-output changes were deferred #8.
- Jonathan S. Katz built and tested the series, suggested more precise trigger-function wording and an explanatory operator-code comment, and observed that pg_dump still emitted EXECUTE PROCEDURE; he also expressed caution about introducing trigger syntax changes into PostgreSQL 11 #10.
- Peter Eisentraut confirmed that all three patches were intended for PostgreSQL 11 and subsequently reported committing them with adjustments, after which Jonathan S. Katz closed the open item #11 #12 #13.
- In February 2019, Peter Eisentraut submitted the deferred pg_dump and ruleutils.c output conversion, together with information-schema and test updates, explaining that the required catalog-version bump had kept this work out of PostgreSQL 11 #14.
- The follow-up landed as 0c1f8f166c with only its catalog-version date updated from #14, and Peter Eisentraut confirmed completion in the thread’s final message #15.