model-writtenrun 1212 - may be wrong, links go to the source messages. Commit-by-commit LLM analysis is in the Commits dialog.
- jian he reported that WITHOUT OVERLAPS rejected domains over otherwise supported range types and proposed parser changes plus a cached base-type classification for executor checks in #1.
- Paul A Jungwirth tested the fix and requested broader domain/range/multirange coverage, consistent naming, and closed/open range notation in #2, prompting expanded tests in #3.
- Paul separated the question of automatically creating multiranges for range domains from this fix and requested clearer, more focused tests in #4 and #5; jian reorganized the tests in #6, defended caching the base-type classification, and retained only one foreign-key scenario.
- Paul argued that foreign-key type interactions still deserved testing and supplied #7, adding domain/non-domain combinations, successful inserts, and clearer explanations while preserving jian's implementation and authorship.
- jian approved the revised patch and requested a parser-comment correction in #8, while Kirill Reshke approved it with an overlap-wording correction in #9; Paul incorporated both in #10 and confirmed the wording change in #11.
- Tom Lane committed #10 as 49f3cb453b, replacing the new cache field with a runtime lookup because its single specialized user did not justify the storage and maintenance costs and the proposed cache updates were incomplete, as explained in #12.
- Tom's closing report in #12 also explained that 49f3cb453b retained only basic domain-over-range and range-over-domain tests to reduce regression runtime and fixed a nearby dropped-column validation bug; the domain-support fix landed with backpatching through PostgreSQL 18, and no remaining patch was identified.