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

From Adam Rich
Subject Re: Locking & concurrency - best practices
Date
Msg-id 008001c85700$e0083570$a018a050$@r@indigodynamic.com
Whole thread Raw
In response to Re: Locking & concurrency - best practices  (Erik Jones <erik@myemma.com>)
Responses Re: Locking & concurrency - best practices  (Erik Jones <erik@myemma.com>)
List pgsql-general
>
>  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.






pgsql-general by date:

Previous
From: Erik Jones
Date:
Subject: Re: Locking & concurrency - best practices
Next
From: Erik Jones
Date:
Subject: Re: Locking & concurrency - best practices