Re: BUG #17140: pg_try_advisory_xact_lock produces a WARNINIG on unsuccessful lock

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: cherio(at)gmail(dot)com
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17140: pg_try_advisory_xact_lock produces a WARNINIG on unsuccessful lock
Date: 2021-08-11 13:50:16
Message-ID: 3968800.1628689816@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

PG Bug reporting form <noreply(at)postgresql(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Cherio 2021-08-11 15:39:29 Re: BUG #17140: pg_try_advisory_xact_lock produces a WARNINIG on unsuccessful lock
Previous Message talk to ben 2021-08-11 13:41:25 Re: BUG #17061: Impossible to query the fields of the tuple created by SEARCH BREADTH FIRST BY .. SET ..