Re: HOT for PostgreSQL 8.3 - Mailing list pgsql-hackers

From Zeugswetter Andreas ADI SD
Subject Re: HOT for PostgreSQL 8.3
Date
Msg-id E1539E0ED7043848906A8FF995BDA57901CAF63C@m0143.s-mxs.net
Whole thread Raw
In response to Re: HOT for PostgreSQL 8.3  ("Pavan Deolasee" <pavan.deolasee@gmail.com>)
Responses Re: HOT for PostgreSQL 8.3  ("Pavan Deolasee" <pavan.deolasee@gmail.com>)
List pgsql-hackers
> > I very much like Hannu's idea, but it does present some issues.
> >
> >
> I too liked Hannu's idea initially, but Tom raised a valid
> concern that it does not address the basic issue of root
> tuples. According to the idea, a DEAD root tuple can be used
> for a subsequent update of the same row.

If you are reusing the existing slot of a root tuple how will that
slot likely have room for an extra pointer and a live tuple ?
If the idea does not cover root reuse we don't need pointers.

Imho we should follow the swing idea. It should even be possible
to point the root to the newest dead tuple during update (if it
was index path), and reuse an older dead slot from the chain.
Then we can limit the chain to number of potentially visible
tuples + root + 2 without vacuum.

Andreas


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: SCMS question
Next
From: Gregory Stark
Date:
Subject: Re: SCMS question