Re: Locking & concurrency - best practices - Mailing list pgsql-general

From Erik Jones
Subject Re: Locking & concurrency - best practices
Date
Msg-id 843CD342-1FEF-49A7-9E01-A254A2174511@myemma.com
Whole thread Raw
In response to Re: Locking & concurrency - best practices  ("Adam Rich" <adam.r@indigodynamic.com>)
List pgsql-general
On Jan 14, 2008, at 4:57 PM, Adam Rich wrote:

>>
>>  From what I can tell, this kind of roll-your-own application level
>> locking system is exactly what advisory locks are for.  Search the
>> archives for the last couple of weeks as I remember someone posting
>> some really helpful functions to assist in using advisory locks.
>>
>> Erik Jones
>
> Yes & No... it depends on the lifetime of the locks you need.  The new
> advisory locks in postgres only live for the duration of your session.
> The ones Andy describes will live past session end, connection end,
> even through database restarts.  And if you're using replication or
> log shipping, the locks will be propagated to partner databases
> as well.
>
> If you need your locks to live past session end, the advisory locks
> won't help you.

Good point.

Erik Jones

DBA | Emma®
erik@myemma.com
800.595.4401 or 615.292.5888
615.292.0777 (fax)

Emma helps organizations everywhere communicate & market in style.
Visit us online at http://www.myemma.com




pgsql-general by date:

Previous
From: "Adam Rich"
Date:
Subject: Re: Locking & concurrency - best practices
Next
From: "Joshua D. Drake"
Date:
Subject: Registration for PostgreSQL Conference East now open