Re: HOT for PostgreSQL 8.3

From: "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com>
To: "Simon Riggs" <simon(at)2ndquadrant(dot)com>
Cc: "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>, "Hannu Krosing" <hannu(at)skype(dot)net>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org, "Pavan Deolasee" <pavan(dot)deolasee(at)enterprisedb(dot)com>, "Nikhil S" <nikhil(dot)sontakke(at)enterprisedb(dot)com>
Subject: Re: HOT for PostgreSQL 8.3
Date: 2007-02-21 18:30:29
Message-ID: 2e78013d0702211030r715d1432ofd88cadd1b8cc4bc@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2/21/07, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>
>
> 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. For a very large table, even if its updated
frequently, it is not unlikely that the same row might not be updated
for a long time. Even when the update happens we would be
constrained by the length of the new version being same or less
than the root tuple OR ability to perform retail-vacuum of the block.

Did you or anybody else got a chance to think about the other idea
I proposed of having indirection from the root line pointer ? As I
mentioned earlier, I myself haven't thought through it completely,
but at the face of it, it looks doable. It would add a four-byte
overhead per live tuple-chain, but IMHO would be much simpler
to implement and not too invasive.

Thanks,
Pavan

--

EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2007-02-21 18:39:48 Re: Column storage positions
Previous Message Andrew Dunstan 2007-02-21 18:16:10 Re: Column storage positions