RE: [GENERAL] update inside transaction violates unique constrain t? - Mailing list pgsql-hackers

From Mikheev, Vadim
Subject RE: [GENERAL] update inside transaction violates unique constrain t?
Date
Msg-id 8F4C99C66D04D4118F580090272A7A23018D16@SECTORBASE1
Whole thread Raw
List pgsql-hackers
> I get an error (which is good).  But, if I do
> 
> #BEGIN;
> #SELECT * FROM name_and_ip WHERE name = 'foo' OR name = 'bar' FOR
>     UPDATE;
> #UPDATE name_and_ip SET ip = '192.168.186.249' where name = 'foo';
> UPDATE 1
> #COMMIT;
> COMMIT

Btree doesn't take into account that tuple was just marked for update
but still alive. Seems it was handled properly in 6.5.X ?
I'll take a look...

Vadim


pgsql-hackers by date:

Previous
From: The Hermit Hacker
Date:
Subject: Re: Damn, pg_proc index corrupted, can't find anythign on REINDEX ...
Next
From: Hannu Krosing
Date:
Subject: Re: SV: Case sensitive field names