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

From Alvaro Herrera
Subject Re: pg_advisory_lock(bigint) vs. LOCK TABLE
Date
Msg-id 20080717161654.GG3934@alvh.no-ip.org
Whole thread Raw
In response to pg_advisory_lock(bigint) vs. LOCK TABLE  (Volkan YAZICI <yazicivo@ttmail.com>)
Responses Re: pg_advisory_lock(bigint) vs. LOCK TABLE  (Volkan YAZICI <yazicivo@ttmail.com>)
Re: pg_advisory_lock(bigint) vs. LOCK TABLE  (Mark Roberts <mailing_lists@pandapocket.com>)
List pgsql-sql
Volkan YAZICI wrote:
> Hi,
> 
> 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.


-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.


pgsql-sql by date:

Previous
From: Florian Weimer
Date:
Subject: Re: Generating table rows from arrays
Next
From: Volkan YAZICI
Date:
Subject: Re: pg_advisory_lock(bigint) vs. LOCK TABLE