RE: btree split logic is fragile in the presence of lar ge index items

> > > Do not add TID to key but store key anywhere in duplicate 
> > > chain and just read lefter child page while positioning index scan,
> > > as we do right now for partial keys?
> > 
> > > This will result in additional reads but I like it much more than
> > > current "logic"...
> >
> 
> What about unique key insertions ?

We'll have to find leftmost key in this case and do what we do now.

Vadim