model-writtenrun 3648 - may be wrong, links go to the source messages. Commit-by-commit LLM analysis is in the Commits dialog.
- In March 2022, Gilles Parc requested a warning that changing a database's owner could leave its former owner unable to connect despite still owning objects inside it; Bruce Momjian and David G. Johnston explained object-specific permissions, and David favored central permissions documentation while noting PUBLIC's default CONNECT privilege #1 #2 #3.
- After Gilles revived the report in January 2024, Laurenz Albe proposed adding a sentence to the general privileges documentation stating that all object privileges transfer with ownership, and Daniel Gustafsson supported the clarification #4 #5 #6.
- David initially disputed that explicit grants transferred, but Laurenz's example and David's own test showed that the new owner inherits the old owner's privilege set, including a revoked UPDATE privilege; David then supported documenting this behavior #9 #10 #12.
- Tom Lane independently demonstrated database ACL transfer, explained that a null ACL produces the equivalent default-privilege behavior, and endorsed Laurenz's proposed wording #17.
- Further discussion established that superuser grants are attributed to the object owner and that even privileges granted to the owner by another role transfer on reassignment; Tom cited compatibility concerns about changing grant attribution, while David demonstrated consolidation of overlapping ACL entries #16 #19 #20.
- Gilles resolved his connection problem after recalling that his organization revoked PUBLIC's default database privileges, meaning the former owner needed fresh grants after reassignment #21.
- David proposed a broader inline rewrite covering ownership, default privileges, and ACL replacement; Laurenz objected to terminology changes, repetition, and excessive implementation detail, and David moved a revised proposal to a separate hackers thread #22 #23 #24.
- Laurenz attached the original concise clarification unchanged, keeping the broader rewrite outside this patchset #25.
- At the last supplied message in November 2025, Josef Šimánek tested the attached patch's claim against database ownership transfer and endorsed it; the thread itself contains no subsequent commit announcement #26.
- Daniel Gustafsson committed the attached wording unchanged on November 12, 2025, as d36acd6f5c and backpatched it through PostgreSQL 14; the separately supplied candidate 4ef048f34d is that change's PostgreSQL 14 backport, so both candidates represent one landed documentation change from #25.