> > 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?!
pgsql-hackers by date
|Next:||From: Mikheev, Vadim||Date: 2000-09-26 19:09:29|
|Subject: RE: pgsql is 75 times faster with my new index scan|
|Previous:||From: Lamar Owen||Date: 2000-09-26 18:08:45|
|Subject: Re: [BUGS] 7.0.2 source rpm failed to compile|