model-writtenrun 6363 - may be wrong, links go to the source messages. Commit-by-commit LLM analysis is in the Commits dialog.
Mar 2018 · 4 entries
- Noah Misch proposed removing PUBLIC's default CREATE privilege on the public schema in March 2018 to address the unsafe combination of a writable schema and the default search_path, initially favoring adoption of the new ACL during upgrades unless users had customized it #1.
- Robert Haas warned about breaking ordinary users' object creation and existing applications during upgrades, while Peter Eisentraut identified that non-superuser database owners could not repair public-schema permissions because the bootstrap superuser owned it #4 #25 #11.
- Tom Lane, Stephen Frost, Alvaro Herrera, and Petr Jelinek explored automatic user-schema creation, but questions about creation timing, opt-outs, and database-owner control remained unresolved, and Peter Eisentraut argued that private user schemas did not fit many collaborative applications #5 #6 #12 #17 #23.
- Noah withdrew the proposal after its mixed reception in March 2018, then reopened it in August 2020 with upgrade-time ACL preservation and no automatic schema creation, narrowing the choice to omitting public entirely or giving its ownership to the database owner #29 #30.
Aug 2020 · 1 entry
- Stephen Frost and Magnus Hagander supported database-owner control as a practical way to improve defaults while retaining usability, and Noah selected that approach with preserved upgrade permissions and unchanged automatic-schema behavior #33 #38 #45.
Oct - Nov 2020 · 2 entries
- After renewed concerns about onboarding and suggestions for separate relation and function search paths, Noah clarified that PUBLIC would retain USAGE while the database owner could create objects or grant access, and explained compatibility problems with splitting search paths #49 #50 #51 #52.
- Bruce Momjian suggested a predefined role for public-schema creation rights, but accepted Noah's objection that an ordinary shared role would grant power across databases rather than track each database's owner #53 #55 #56.
Feb - Mar 2021 · 3 entries
- Noah submitted the first patch in February 2021 with four prerequisites maintained in two other threads, using the special pg_database_owner role and assigning ownership through pg_namespace.dat; pg_dump reproduced source ownership and ACLs by comparing them with the destination defaults #57.
- Testing the new ACL broke thirteen core regression tests, so Noah restored the old ACL early in that suite to avoid extensive expected-output changes that would complicate backpatching, while adapting other suites to exercise the new defaults #57.
- As prerequisites landed, Noah first reduced the testing rollup and then posted a standalone rebased patch in June 2021, retaining the same public-schema policy #58 #60.
Jun 2021 · 1 entry
- Noah subsequently committed #60 as b073c3ccd0, with release-reference updates and a catalog-version bump, completing the default ACL and ownership change for PostgreSQL 15 while preserving existing ownership and permissions during upgrades.
Sep 2021 · 1 entry
- Peter Eisentraut reviewed the final patch, reported successful upgrade tests, and requested release-number corrections; Noah agreed to make those corrections, and Peter marked the work ready for committer in the thread's final message #61 #62 #63.