> > > > 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
- Re: [HACKERS] pgsql is 75 times faster with my new index sc... Hannu Krosing
- Re: [HACKERS] pgsql is 75 times faster with my new ind... Philip Warner
- Re: [HACKERS] pgsql is 75 times faster with my new ind... Hiroshi Inoue
- Re: [HACKERS] pgsql is 75 times faster with my new ind... Bruce Momjian
- Re: [HACKERS] pgsql is 75 times faster with my new... Devik
- Re: [HACKERS] pgsql is 75 times faster with my... Bruce Momjian
- Re: [HACKERS] pgsql is 75 times faster wit... Hannu Krosing
- Re: [HACKERS] pgsql is 75 times faste... Devik
- Re: [HACKERS] pgsql is 75 times faste... Bruce Momjian
- RE: [HACKERS] pgsql is 75 times faster with my new index sc... Mikheev, Vadim
- RE: [HACKERS] pgsql is 75 times faster with my new index sc... Mikheev, Vadim
- RE: [HACKERS] pgsql is 75 times faster with my new index sc... Mikheev, Vadim
- RE: [HACKERS] pgsql is 75 times faster with my new index sc... Mikheev, Vadim
- RE: [HACKERS] pgsql is 75 times faster with my new index sc... Mikheev, Vadim