| From: | "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com> |
|---|---|
| To: | "Bruce Momjian" <bruce(at)momjian(dot)us> |
| Cc: | "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: HOT is applied |
| Date: | 2007-09-21 08:19:37 |
| Message-ID: | 2e78013d0709210119p360f94d0y26c0986e969ec479@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 9/21/07, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>
>
> This might be a simplistic question but if the page is +90% full and
> there is a long-lived transaction, isn't Postgres going to try pruning
> on each page read access?
>
>
The way it stands today, yes. Thats one reason why we are seeing
the performance drop in this particular case.
I liked the earlier proposed idea of storing the xid in the page header
to quickly tell us whether its worth pruning the page.
Thanks,
Pavan
--
Pavan Deolasee
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2007-09-21 08:37:57 | Re: HOT is applied |
| Previous Message | Gokulakannan Somsundaram | 2007-09-21 08:05:31 | Re: Improving the Performance of Full Table Updates |