Re: BUG #10429: the same update return different result - Mailing list pgsql-bugs

From Claudio Nieder
Subject Re: BUG #10429: the same update return different result
Date
Msg-id CB2BE94E-FEE1-4E0D-94A8-547CFF529853@inodes.ch
Whole thread Raw
In response to Re: BUG #10429: the same update return different result  (rodriguez <rodriguez@ort.edu.uy>)
Responses Re: BUG #10429: the same update return different result  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Hi,
>> postgres=3D# update t1 set c1 =3D c1 +1;
> This controls whether the constraint can be deferred. A constraint =
that is not deferrable will be checked immediately after every command.
>=20
My understanding would have been, that "update t1 set c1=3Dc1+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.=20

claudio
--=20
Claudio Nieder  .  mailto:claudio.nieder@inodes.ch  .  http://inodes.ch/
iNodes AG  .  Loogartenstrasse 14  .  CH-8048 Z=FCrich  .  +41 43 960 =
0066

pgsql-bugs by date:

Previous
From: m.sakrejda@gmail.com
Date:
Subject: BUG #10432: failed to re-find parent key in index
Next
From: Tom Lane
Date:
Subject: Re: BUG #10429: the same update return different result