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

I can not reproduce it any more.
There is a chance there were more forces at play when I was getting the
lock warning message.
Please forgive the disturbance.

On Wed, Aug 11, 2021 at 9:50 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> 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
>