Re: Open issues for HOT patch - Mailing list pgsql-hackers

From Pavan Deolasee
Subject Re: Open issues for HOT patch
Date
Msg-id 2e78013d0709190211i5e01a4bm1c3a205615f1f87@mail.gmail.com
Whole thread Raw
In response to Re: Open issues for HOT patch  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-hackers


On 9/19/07, Simon Riggs <simon@2ndquadrant.com> wrote:

In your last post you mentioned multiple UPDATEs. Pruning multiple times
for successive UPDATEs isn't going to release more space, so why do it?


I guess the point is when you do the first update, there is enough free space
in the page and hence we won't prune the page. We run out of free space for
subsequent updates and want to prune, but now can't prune because executor
is holding a pin on the buffer.

Thanks,
Pavan

--
Pavan Deolasee
EnterpriseDB     http://www.enterprisedb.com

pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Open issues for HOT patch
Next
From: Heikki Linnakangas
Date:
Subject: Re: Open issues for HOT patch