Re: pg_advisory_lock(bigint) vs. LOCK TABLE

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Volkan YAZICI <yazicivo(at)ttmail(dot)com>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: pg_advisory_lock(bigint) vs. LOCK TABLE
Date: 2008-07-17 16:16:54
Message-ID: 20080717161654.GG3934@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Volkan YAZICI 2008-07-18 05:26:28 Re: pg_advisory_lock(bigint) vs. LOCK TABLE
Previous Message Florian Weimer 2008-07-17 11:44:24 Re: Generating table rows from arrays