> Hmm,it seems that both current and REL7_0_PATCHES
> have already been changed.
> I committed the the change to current tree and
> asked Tatsuo to commit it to REL7_0_PATCHES tree.
I also committed current -:))
Vadim
"Mikheev, Vadim" wrote:
> > > 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 ?
> >
> > Nope. It has been broken a long time...
>
> Hmm, as I remember, Hiroshi fixed something in this area for 7.0.X.
> Hiroshi?
>
> > 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 ?
>
> Nope. It has been broken a long time...
Hmm, as I remember, Hiroshi fixed something in this area for 7.0.X.
Hiroshi?
Probably, his fix somehow disappeared
> > 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 ?
>
> Nope. It has been broken a long time...
Ops. Ok...
Vadim
"Mikheev, Vadim" wrote:
>
> > 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
>
> Btre
