I have added this email's URL to TODO under tuple visibility.
---
Karl Schnaitter wrote:
> Sometime last year, a discussion started about including visibility
> metadata to avoid heap fetches during an index scan:
>
> http
"Heikki Linnakangas" <[EMAIL PROTECTED]> writes:
> I'm not sure I have enough time to get all that done for 8.4, it's looking bad
> at the moment, so help would be much appreciated. If you don't agree with
> taking the visibility map approach, I would suggest working on the indexam API
> changes f
Karl Schnaitter wrote:
The main difference between (1) & (4) is that (1) will sometimes require
heap lookups and (4) never will. Moreover, the heap lookups in (1) will
be difficult for the optimizer to estimate, unless some special
statistics can be maintained for this purpose.
Yeah, we certa
Gregory Stark wrote:
(1) & (4) require an UPDATE or DELETE to twiddle the old index tuple. Tom has
noted (in the linked message) that this is not reliable if the index has any
expression-valued columns, because it is not always possible to find the old
index entry. For this reason, the proposed p
"Karl Schnaitter" <[EMAIL PROTECTED]> writes:
"Karl Schnaitter" <[EMAIL PROTECTED]> writes:
> (1) & (4) require an UPDATE or DELETE to twiddle the old index tuple. Tom has
> noted (in the linked message) that this is not reliable if the index has any
> expression-valued columns, because it is not
Sometime last year, a discussion started about including visibility
metadata to avoid heap fetches during an index scan:
http://archives.postgresql.org/pgsql-patches/2007-10/msg00166.php
http://archives.postgresql.org/pgsql-patches/2008-01/msg00049.php
I think the last discussion on this was in
