Horton

Re: installcheck-world concurrency issues

Michael Paquier <michael@paquier.xyz>

View thread View on postgr.es
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-24T02:24:46Z
Lists: pgsql-hackers 
On Thu, Oct 06, 2022 at 01:52:46PM +0900, Michael Paquier wrote:
> For the archives' sake: this has been applied as of 6a20b04 and
> c3315a7.

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.
--
Michael

Commits

  1. tests: Rename conflicting role names

  2. tests: Restrict pg_locks queries in advisory_locks.sql to current database