Re: Counterintuitive locking behavior

From: Thomas Kellerer <spam_eater(at)gmx(dot)net>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Counterintuitive locking behavior
Date: 2013-01-06 08:52:07
Message-ID: kcbdvh$kv8$1@ger.gmane.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message kenyon 2013-01-06 09:57:34 currval of sequence xxx_seq is not yet defined in this session?
Previous Message Boszormenyi Zoltan 2013-01-06 07:11:31 Re: Counterintuitive locking behavior