pgsql: tests: Restrict pg_locks queries in advisory_locks.sql to curren

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: tests: Restrict pg_locks queries in advisory_locks.sql to curren
Date: 2024-09-26 04:47:25
Message-ID: E1stgPU-000yQM-Js@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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

Otherwise testing an existing installation can fail, if there are other locks,
e.g. from one of the isolation tests.

This was originally applied as c3315a7da57b in 16~, but it is possible
to see this test fail depending on the concurrent activity for older
active branches.

Reviewed-by: Michael Paquier <michael(at)paquier(dot)xyz>
Discussion: https://postgr.es/m/20221003234111.4ob7yph6r4g4ywhu@awork3.anarazel.de
Backpatch-through: 12

Branch
------
REL_13_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/f232d7c6827c30e8f464dfa31cbe243ff6002ba9
Author: Andres Freund <andres(at)anarazel(dot)de>

Modified Files
--------------
src/test/regress/expected/advisory_lock.out | 31 ++++++++++++++--------------
src/test/regress/sql/advisory_lock.sql | 32 +++++++++++++++--------------
2 files changed, 33 insertions(+), 30 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2024-09-26 08:18:49 Re: pgsql: Implement pg_wal_replay_wait() stored procedure
Previous Message Nathan Bossart 2024-09-25 16:20:06 pgsql: Remove extra whitespace in pg_upgrade status message.