Re: installcheck-world concurrency issues
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Andres Freund <andres@anarazel.de>
Cc: pgsql-hackers@postgresql.org, Peter Geoghegan <pg@bowt.ie>, Peter Eisentraut <peter.eisentraut@enterprisedb.com>, Corey Huinker <corey.huinker@gmail.com>
Date: 2024-09-26T04:47:52Z
Lists: pgsql-hackers
On Tue, Sep 24, 2024 at 11:24:46AM +0900, Michael Paquier wrote: > Corey (added in CC.), has noticed that the issue fixed by c3315a7 in > 16~ for advisory locks is not complicated to reach, leading to > failures in some of our automated internal stuff. A cherry-pick of > c3315a7 works cleanly across 12~15. Would there be any objections if > I were to backpatch this part down to 12? > > The problems fixed by 6a20b04 have not really been an issue here, > hence I'd rather let things be as they are for the conflicting role > names. Hearing nothing, done. -- Michael
Commits
-
tests: Rename conflicting role names
- d90aa68c96a8 14.21 landed
- aa2ec0403d0a 15.16 landed
- 6a20b04f0408 16.0 landed
-
tests: Restrict pg_locks queries in advisory_locks.sql to current database
- 81487c83bed9 12.21 landed
- f232d7c6827c 13.17 landed
- e750e413325e 14.14 landed
- 3981fd5869fc 15.9 landed
- c3315a7da57b 16.0 landed