Re: pg_advisory_lock(bigint) vs. LOCK TABLE

From: Volkan YAZICI <yazicivo(at)ttmail(dot)com>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: pg_advisory_lock(bigint) vs. LOCK TABLE
Date: 2008-07-18 05:26:28
Message-ID: 877ibj3gqj.fsf@alamut.mobiliz.com.tr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

On Thu, 17 Jul 2008, Alvaro Herrera <alvherre(at)commandprompt(dot)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.

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Tom Lane 2008-07-18 05:40:37 Re: pg_advisory_lock(bigint) vs. LOCK TABLE
Previous Message Alvaro Herrera 2008-07-17 16:16:54 Re: pg_advisory_lock(bigint) vs. LOCK TABLE