From: Tom Lane <tgl@sss.pgh.pa.us>
To: cherio@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17140: pg_try_advisory_xact_lock produces a WARNINIG on unsuccessful lock
Date: Wed, 11 Aug 2021 09:50:16 -0400
Message-ID: <3968800.1628689816@sss.pgh.pa.us> (raw)
In-Reply-To: <17140-38f50de605441268@postgresql.org>
References: <17140-38f50de605441268@postgresql.org>
PG Bug reporting form <noreply@postgresql.org> writes:
> Function "pg_try_advisory_xact_lock" triggers a WARNING message when the
> lock is already owned by someone else.
I failed to duplicate this behavior. I did this in session A:
regression=# begin;
BEGIN
regression=*# select pg_try_advisory_xact_lock(1);
pg_try_advisory_xact_lock
---------------------------
t
(1 row)
then this in session B:
regression=# select pg_try_advisory_xact_lock(1);
pg_try_advisory_xact_lock
---------------------------
f
(1 row)
No warning...
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, cherio@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17140: pg_try_advisory_xact_lock produces a WARNINIG on unsuccessful lock
In-Reply-To: <3968800.1628689816@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox