Re: Locking & concurrency - best practices
От | Erik Jones |
---|---|
Тема | Re: Locking & concurrency - best practices |
Дата | |
Msg-id | 843CD342-1FEF-49A7-9E01-A254A2174511@myemma.com обсуждение исходный текст |
Ответ на | Re: Locking & concurrency - best practices ("Adam Rich" <adam.r@indigodynamic.com>) |
Список | 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 по дате отправления: