| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Volkan YAZICI <yazicivo(at)ttmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: pg_advisory_lock(bigint) vs. LOCK TABLE |
| Date: | 2008-07-18 05:40:37 |
| Message-ID: | 10590.1216359637@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
Volkan YAZICI <yazicivo(at)ttmail(dot)com> writes:
> On Thu, 17 Jul 2008, Alvaro Herrera <alvherre(at)commandprompt(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lennin Caro | 2008-07-18 14:04:32 | Re: How to GROUP results BY month |
| Previous Message | Volkan YAZICI | 2008-07-18 05:26:28 | Re: pg_advisory_lock(bigint) vs. LOCK TABLE |