Re: Further open item (Was: Status of 7.2) - Mailing list pgsql-hackers

From Tille, Andreas
Subject Re: Further open item (Was: Status of 7.2)
Date
Msg-id Pine.LNX.4.33.0111191303570.27841-100000@wr-linux02.rki.ivbb.bund.de
Whole thread Raw
In response to Re: Further open item (Was: Status of 7.2)  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
On Fri, 16 Nov 2001, Bruce Momjian wrote:

> I personally would like to have index scans that look up heap rows
> record the heap expired status into the index entry via one bit of
> storage.  This will not _prevent_ checking the heap but it will prevent
> heap lookups for index entries that have been exipred for a long time.
> However, with the new vacuum, and perhaps autovacuum coming soon, may be
> little need for this optimization.
>
> The underlying problem the user is seeing is how to _know_ an index
> tuple is valid without checking the heap, and I don't see how to do that
> unless we start storing the transaction id in the index tuple, and that
> requires extra storage.
For my special case I think doubling main memory is about the same
price as a MS SQL server license.  I can´t say which further problems
might occure.

Kind regards
       Andreas.


pgsql-hackers by date:

Previous
From: "Tille, Andreas"
Date:
Subject: Re: Further open item (Was: Status of 7.2)
Next
From: "Tille, Andreas"
Date:
Subject: Re: Further open item (Was: Status of 7.2)