Re: Counterintuitive locking behavior - Mailing list pgsql-general

From Thomas Kellerer
Subject Re: Counterintuitive locking behavior
Date
Msg-id kcbdvh$kv8$1@ger.gmane.org
Whole thread Raw
In response to Counterintuitive locking behavior  (Chris Travers <chris.travers@gmail.com>)
List 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 by date:

Previous
From: Boszormenyi Zoltan
Date:
Subject: Re: Counterintuitive locking behavior
Next
From: kenyon
Date:
Subject: currval of sequence xxx_seq is not yet defined in this session?