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

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: BUG #17140: pg_try_advisory_xact_lock produces a WARNINIG on unsuccessful lock
Дата
Msg-id 3968800.1628689816@sss.pgh.pa.us
обсуждение исходный текст
Ответ на BUG #17140: pg_try_advisory_xact_lock produces a WARNINIG on unsuccessful lock  (PG Bug reporting form <noreply@postgresql.org>)
Ответы Re: BUG #17140: pg_try_advisory_xact_lock produces a WARNINIG on unsuccessful lock  (Cherio <cherio@gmail.com>)
Список pgsql-bugs
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



В списке pgsql-bugs по дате отправления:

Предыдущее
От: talk to ben
Дата:
Сообщение: Re: BUG #17061: Impossible to query the fields of the tuple created by SEARCH BREADTH FIRST BY .. SET ..
Следующее
От: Cherio
Дата:
Сообщение: Re: BUG #17140: pg_try_advisory_xact_lock produces a WARNINIG on unsuccessful lock