> > The last step could be done in two ways. First by limiting
> > number of indices for one table we can store coresponding
> > indices' TIDs in each heap tuple. The update is then simple
> > taking one disk write.
> 
> Why limit it ? One could just save an tid array in each tuple .

And update *entire* heap after addition new index?!

Vadim

Reply via email to