Re: Locking & concurrency - best practices

Поиск
Список
Период
Сортировка
От Adam Rich
Тема Re: Locking & concurrency - best practices
Дата
Msg-id 008001c85700$e0083570$a018a050$@r@indigodynamic.com
обсуждение исходный текст
Ответ на Re: Locking & concurrency - best practices  (Erik Jones <erik@myemma.com>)
Ответы Re: Locking & concurrency - best practices  (Erik Jones <erik@myemma.com>)
Список 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 по дате отправления:

Предыдущее
От: Erik Jones
Дата:
Сообщение: Re: Locking & concurrency - best practices
Следующее
От: Erik Jones
Дата:
Сообщение: Re: Locking & concurrency - best practices