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

From Tom Lane
Subject Re: pg_advisory_lock(bigint) vs. LOCK TABLE
Date
Msg-id 10590.1216359637@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_advisory_lock(bigint) vs. LOCK TABLE  (Volkan YAZICI <yazicivo@ttmail.com>)
List pgsql-sql
Volkan YAZICI <yazicivo@ttmail.com> writes:
> On Thu, 17 Jul 2008, Alvaro Herrera <alvherre@commandprompt.com> writes:
>> 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.

Advisory locks are defined as locking application-defined identifiers.
Why would you expect them to conflict with system locks, and what would
be the relationship exactly?
        regards, tom lane


pgsql-sql by date:

Previous
From: Volkan YAZICI
Date:
Subject: Re: pg_advisory_lock(bigint) vs. LOCK TABLE
Next
From: Lennin Caro
Date:
Subject: Re: How to GROUP results BY month