| From: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
|---|---|
| To: | Hannu Krosing <hannu(at)tm(dot)ee> |
| Cc: | devik(at)cdi(dot)cz, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pgsql is 75 times faster with my new index scan |
| Date: | 2000-09-26 10:59:46 |
| Message-ID: | 39D081A2.9059FAC9@tpf.co.jp |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hannu Krosing wrote:
>
> >
> > TODO:
> > - add HeapTupleHeaderData into each IndexTupleData
> > - change code to reflect above
> > - when deleting-updating heap then also update tuples'
> > HeapTupleHeaderData in indices
>
> I doubt everyone would like trading query speed for insert/update
> speed plus index size
>
> Perhaps this could be implemented as a special type of index which
> you must explicitly specify at create time ?
>
> > 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 .
>
Indice's TIDs are transient.
Isn't it useless to store indice's TIDs ?
Regards.
Hiroshi Inoue
| From | Date | Subject | |
|---|---|---|---|
| Next Message | devik | 2000-09-26 11:13:40 | Re: pgsql is 75 times faster with my new index scan |
| Previous Message | Hannu Krosing | 2000-09-26 10:35:24 | Re: Case sensitive field names |