> > 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 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. -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026
- [HACKERS] pgsql is 75 times faster with my new index scan devik
- Re: [HACKERS] pgsql is 75 times faster with my new i... Alfred Perlstein
- Re: [HACKERS] pgsql is 75 times faster with my new i... Hannu Krosing
- Re: [HACKERS] pgsql is 75 times faster with my n... Philip Warner
- Re: [HACKERS] pgsql is 75 times faster with ... devik
- [HACKERS] Deep Trouble Abe Asghar
- Re: [HACKERS] pgsql is 75 times faster with my n... Hiroshi Inoue
- Re: [HACKERS] pgsql is 75 times faster with my n... Bruce Momjian
- Re: [HACKERS] pgsql is 75 times faster with ... Devik
- Re: [HACKERS] pgsql is 75 times faster w... Bruce Momjian
- Re: [HACKERS] pgsql is 75 times fas... Hannu Krosing
- Re: [HACKERS] pgsql is 75 times... Devik
- Re: [HACKERS] pgsql is 75 times... Bruce Momjian
- RE: [HACKERS] pgsql is 75 times faster with my new i... Mikheev, Vadim
- RE: [HACKERS] pgsql is 75 times faster with my new i... Mikheev, Vadim