| From: | "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | "Zeugswetter Andreas ADI SD" <ZeugswetterA(at)spardat(dot)at> |
| Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Frequent Update Project: Design Overview ofHOTUpdates |
| Date: | 2006-11-10 17:36:46 |
| Message-ID: | 1163180206.3634.810.camel@silverbirch.site |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 2006-11-10 at 17:00 +0100, Zeugswetter Andreas ADI SD wrote:
> > > 2. locking should be easier if only the original heap page is
> involved.
> >
> > Yes, but multi-page update already happens now, so HOT is not
> > different on that point.
>
> I was thinking about the case when you "pull back" a tuple, which seems
> to be more
> difficult than what we have now.
Well, it sounds like it would be really bad, at least thats what I
thought at first. We tried it anyway and performance shows it aint that
bad.
> PS: I think it is great that you are doing all this work and explaining
> it for us. Thanks.
Thanks for your feedback; I'm certain we'll be able to improve on where
HOT is now with some objective thinking.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2006-11-10 18:38:12 | Re: Frequent Update Project: Design Overview of |
| Previous Message | Zeugswetter Andreas ADI SD | 2006-11-10 16:04:54 | Re: Frequent Update Project: Design Overview of HOTUpdates |