Re: Counterintuitive locking behavior

Поиск
Список
Период
Сортировка
От Thomas Kellerer
Тема Re: Counterintuitive locking behavior
Дата
Msg-id kcbdvh$kv8$1@ger.gmane.org
обсуждение исходный текст
Ответ на Counterintuitive locking behavior  (Chris Travers <chris.travers@gmail.com>)
Список pgsql-general
Chris Travers wrote on 06.01.2013 03:18:
> i.e. where on UPDATE foo, all rows selected from foo during the
> update are locked unless the subselect specifically states
> otherwise.

That would strike *me* as wrong.

The UPDATE should only lock the rows that were actually updated, not those that were selected.

Thomas


В списке pgsql-general по дате отправления:

Предыдущее
От: Boszormenyi Zoltan
Дата:
Сообщение: Re: Counterintuitive locking behavior
Следующее
От: kenyon
Дата:
Сообщение: currval of sequence xxx_seq is not yet defined in this session?