| From: | "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com> |
|---|---|
| To: | "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
| Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Open issues for HOT patch |
| Date: | 2007-09-19 09:11:56 |
| Message-ID: | 2e78013d0709190211i5e01a4bm1c3a205615f1f87@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 9/19/07, Simon Riggs <simon(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2007-09-19 09:53:27 | Re: Open issues for HOT patch |
| Previous Message | Heikki Linnakangas | 2007-09-19 08:46:12 | Re: Open issues for HOT patch |