> 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
