| From: | devik(at)cdi(dot)cz |
|---|---|
| To: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
| Cc: | Hannu Krosing <hannu(at)tm(dot)ee>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pgsql is 75 times faster with my new index scan |
| Date: | 2000-09-26 11:13:40 |
| Message-ID: | 39D084E4.80383884@cdi.cz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > > 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 .
because when you add new index you had to rescan whole
heap and grow the tid array ..
> Indice's TIDs are transient.
> Isn't it useless to store indice's TIDs ?
but yes Hiroshi is right. Index TID is transient. I first looked
into pg sources two weeks ago so I have still holes in my knowledge.
So that only solution is to traverse it ..
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Philip Warner | 2000-09-26 11:46:16 | Re: pgsql is 75 times faster with my new index scan |
| Previous Message | Hiroshi Inoue | 2000-09-26 10:59:46 | Re: pgsql is 75 times faster with my new index scan |