| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: HOT patch - version 15 |
| Date: | 2007-09-05 22:15:36 |
| Message-ID: | 26448.1189030536@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Tom Lane wrote:
>> Uh, why would any of this code at all execute during a pure lookup?
> No idea. It seems an index lookup tries to prune a heap chain, and he
> was asking if it should look at other chains on the page; I said not.
> Whether the index lookup should prune the heap chain is another issue.
ISTM the only time we should be doing HOT cleanup work is when we are
trying to insert a new tuple on that page --- and maybe even only when
we try and it doesn't fit straight off. Otherwise you're pushing
maintenance work into foreground query pathways, which is exactly where
I don't think we should be headed.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Treat | 2007-09-05 22:35:31 | Re: [PATCHES] Lazy xid assignment V4 |
| Previous Message | Tom Lane | 2007-09-05 22:12:55 | Re: Lazy xid assignment V4 |