]> git.ipfire.org Git - thirdparty/postgresql.git/commit
tests: Restrict pg_locks queries in advisory_locks.sql to current database
authorAndres Freund <andres@anarazel.de>
Wed, 5 Oct 2022 17:44:38 +0000 (10:44 -0700)
committerMichael Paquier <michael@paquier.xyz>
Thu, 26 Sep 2024 04:46:40 +0000 (13:46 +0900)
commitf232d7c6827c30e8f464dfa31cbe243ff6002ba9
treecc2f5eb815e762cee4e10f93f156373dd006018d
parent9db4598c9c984d41896d517ff53b7b0cfbb3dc2e
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@paquier.xyz>
Discussion: https://postgr.es/m/20221003234111.4ob7yph6r4g4ywhu@awork3.anarazel.de
Backpatch-through: 12
src/test/regress/expected/advisory_lock.out
src/test/regress/sql/advisory_lock.sql