model-writtenrun 5945 - may be wrong, links go to the source messages. Commit-by-commit LLM analysis is in the Commits dialog.
- Paul Martinez proposed optional column lists for foreign-key SET NULL and SET DEFAULT actions so composite keys could retain tenant identifiers while clearing another referencing column; his initial patch supported both UPDATE and DELETE actions #1.
- After the initial submission remained unreviewed for several months, Peter Eisentraut questioned the meaning of fixed column lists for UPDATE actions and recommended limiting the feature to DELETE #4; Paul disputed the SQL-standard interpretation but supplied both full and DELETE-only alternatives because the semantics remained uncertain #6.
- Paul refreshed both alternatives, removed the catalog-version change and completed column-list propagation in the full variant #8; Zhihong Yu then questioned the plan names #9, prompting consistent renaming and an explanation of why UPDATE and DELETE require separate cached plans #10.
- Peter extracted the existing referential-action syntax documentation from #10 into db9f287711, correcting the CREATE TABLE synopsis and adding the equivalent ALTER TABLE text while leaving the new column-list feature for later #11.
- Peter reviewed the DELETE-only implementation and supplied fixup patches, requesting NULL instead of an empty catalog array for default behavior, consolidated parser checks, clearer plan names and exclusion of unrelated node-output support #11.
- Paul incorporated Peter's changes and continued with only the DELETE-only alternative #12, then applied Zhihong's wording and variable-scope corrections in the final submission #13 #14.
- Peter questioned whether the documentation example actually needed composite keys and briefly postponed the otherwise acceptable patch while the use case was clarified #15 #16.
- Matthias van de Meent defended composite keys as protection against cross-tenant references #17, and Paul explained the sharding, integrity and indexing motivations while agreeing that the example should identify rows using both key columns #18.
- Peter committed #14 as d6f96ed94e with light documentation and supporting-code edits, including the revised tenant example, and announced completion in the final message #19; DELETE column lists had landed, while UPDATE column lists remained outside the accepted scope.