| From: | Devik <devik(at)server(dot)cdi(dot)cz> |
|---|---|
| To: | Hannu Krosing <hannu(at)tm(dot)ee> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, 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 13:23:55 |
| Message-ID: | Pine.LNX.4.10.10010171521380.16485-100000@luxik.cdi.cz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > > > 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 ?
Yes. This was the main point ! For small number of records the
current method is fast enough. The direct index scan is useful
for big tables and doing scan over large parts of them (like
in aggregates).
devik
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2000-10-17 13:33:48 | Re: length coerce for bpchar is broken since 7.0 |
| Previous Message | Bruce Momjian | 2000-10-17 12:05:17 | Re: pgsql is 75 times faster with my new index scan |