Re: pg_advisory_lock(bigint) vs. LOCK TABLE - Mailing list pgsql-sql

From Volkan YAZICI
Subject Re: pg_advisory_lock(bigint) vs. LOCK TABLE
Date
Msg-id 877ibj3gqj.fsf@alamut.mobiliz.com.tr
Whole thread Raw
In response to Re: pg_advisory_lock(bigint) vs. LOCK TABLE  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: pg_advisory_lock(bigint) vs. LOCK TABLE  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-sql
On Thu, 17 Jul 2008, Alvaro Herrera <alvherre@commandprompt.com> writes:
> Volkan YAZICI wrote:
>> What's the difference between below two queue implementations?
>
> They are two different lock spaces.  pg_advisory_lock does not conflict
> with regular system locks, whereas LOCK TABLE does.

Is this documented in somewhere? I couldn't figure out that from the
documentation.


Regards.


pgsql-sql by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: pg_advisory_lock(bigint) vs. LOCK TABLE
Next
From: Tom Lane
Date:
Subject: Re: pg_advisory_lock(bigint) vs. LOCK TABLE