Re: BUG #10429: the same update return different result

From: Claudio Nieder <claudio(dot)nieder(dot)lists(at)inodes(dot)ch>
To: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #10429: the same update return different result
Date: 2014-05-23 19:29:03
Message-ID: CB2BE94E-FEE1-4E0D-94A8-547CFF529853@inodes.ch
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,
>> postgres=# update t1 set c1 = c1 +1;
> This controls whether the constraint can be deferred. A constraint that is not deferrable will be checked immediately after every command.
>
My understanding would have been, that "update t1 set c1=c1+1;" is ONE command, so even in the NOT DEFERRABLE case the check would occur only after both values were changed and as such not find any violation of the constraint.

claudio
--
Claudio Nieder . mailto:claudio(dot)nieder(at)inodes(dot)ch . http://inodes.ch/
iNodes AG . Loogartenstrasse 14 . CH-8048 Zürich . +41 43 960 0066

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2014-05-23 19:34:05 Re: BUG #10429: the same update return different result
Previous Message m.sakrejda 2014-05-23 17:52:17 BUG #10432: failed to re-find parent key in index