From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: cherio@gmail.com
Subject: BUG #17140: pg_try_advisory_xact_lock produces a WARNINIG on unsuccessful lock
Date: Tue, 10 Aug 2021 18:29:45 +0000
Message-ID: <17140-38f50de605441268@postgresql.org> (raw)
The following bug has been logged on the website:
Bug reference: 17140
Logged by: Yuri Cherio
Email address: cherio@gmail.com
PostgreSQL version: 13.3
Operating system: Ubuntu Linux 20.04
Description:
Function "pg_try_advisory_xact_lock" triggers a WARNING message when the
lock is already owned by someone else. The documentation explicitly mentions
warnings on advisory unlock functions and those are understandable - the
developer should not try to unlock what's not owned.
However the advisory lock functions are there for this specific reason -
test whether a resource is locked or not. A negative test should not produce
a WARNING.
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: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, cherio@gmail.com
Subject: Re: BUG #17140: pg_try_advisory_xact_lock produces a WARNINIG on unsuccessful lock
In-Reply-To: <17140-38f50de605441268@postgresql.org>
* 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