| From: | Hannu Krosing <hannu(at)tm(dot)ee> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Devik <devik(at)server(dot)cdi(dot)cz>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pgsql is 75 times faster with my new index scan |
| Date: | 2000-10-17 11:16:24 |
| Message-ID: | 39EC3508.C9F9D350@tm.ee |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian wrote:
>
> > > > I doubt everyone would like trading query speed for insert/update
> > > > speed plus index size
> > >
> > > If he is scanning through the entire index, he could do a sequential
> > > scan of the table, grab all the tid transaction status values, and use
> > > those when viewing the index. No need to store/update the transaction
> > > status in the index that way.
> >
> > Huh ? How ? It is how you do it now. Do you expect
> > load several milion transaction statuses into memory,
> > then scan index and lookup these values ?
> > Missed I something ?
> > devik
> >
> >
>
> Not sure. I figured they were pretty small values.
IIRC the whole point was to avoid scanning the table ?
-------------
Hannu
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Poul L. Christiansen | 2000-10-17 11:28:16 | Re: Full text indexing (Question/request) |
| Previous Message | Gilles DAROLD | 2000-10-17 11:12:51 | Re: [GENERAL] PL/Perl compilation error |