model-writtenrun 7132 - may be wrong, links go to the source messages. Commit-by-commit LLM analysis is in the Commits dialog.
- Andres Freund reported concurrent installcheck-world failures caused by shared role names and cross-database advisory-lock queries, attaching two fixes plus the Meson installcheck prototype that exposed them and reporting successful repeated runs in #1.
- Michael Paquier endorsed the role cleanup, suggested renaming regress_user11, asked about the source of advisory-lock interference, and reported that the Meson running setup worked in #2; Andres retained the core regression naming convention and explained that concurrent isolation tests caused the interference while prepared_xacts.sql ran in a separate group in #3.
- Peter Eisentraut distinguished tests that expose listening servers from tests that alter an existing instance in #4, while Andres emphasized the danger of damaging existing clusters in #5; the proposal to gate unsafe_tests through PG_TEST_EXTRA remained unresolved.
- Andres committed the role-renaming patch unchanged as 6a20b04f04 and the advisory-lock filtering patch unchanged as c3315a7da5, both from #1, with Michael recording their application in #6; the accompanying Meson prototype was supplied for context and has no recorded landing in this thread.
- Nearly two years later, Michael reported that Corey had encountered advisory-lock failures in internal automation and proposed backpatching c3315a7da5 to PostgreSQL 12–15 after confirming clean cherry-picks, while declining additional role-name backpatches because those failures had not affected them, in #7.
- Michael confirmed completion of the advisory-lock backpatches after no objections in #8, closing the thread with both original fixes landed and the advisory-lock fix extended to the older branches.