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 E1539E0ED7043848906A8FF995BDA57901CAF686@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
> > Imho we should follow the swing idea.
>
>
> Yes, thats one option. Though given a choice I would waste
> four bytes in the heap-page than inserting a new index entry.

No question about that. My point was, that it would mean wasting
the 2 (2 must be enough for a slot pointer) bytes on every heap tuple,
hot or not. And then the decision is not so obvious anymore.
If you don't have the room for the back pointer on every slot,
there is no room to add one later.

Andreas


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Grouped Index Tuples
Next
From: Markus Schiltknecht
Date:
Subject: Re: SCMS question