Re: Frequent Update Project: Design Overview of HOTUpdates - Mailing list pgsql-hackers

From Zeugswetter Andreas ADI SD
Subject Re: Frequent Update Project: Design Overview of HOTUpdates
Date
Msg-id E1539E0ED7043848906A8FF995BDA579017C092F@m0143.s-mxs.net
Whole thread Raw
In response to Re: Frequent Update Project: Design Overview of HOTUpdates  ("Simon Riggs" <simon@2ndquadrant.com>)
Responses Re: Frequent Update Project: Design Overview ofHOTUpdates  ("Simon Riggs" <simon@2ndquadrant.com>)
List pgsql-hackers
> > 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.

Andreas

PS: I think it is great that you are doing all this work and explaining
it for us. Thanks.


pgsql-hackers by date:

Previous
From: "Zeugswetter Andreas ADI SD"
Date:
Subject: Re: Frequent Update Project: Design Overview of HOT Updates
Next
From: "Zeugswetter Andreas ADI SD"
Date:
Subject: Re: Frequent Update Project: Design Overview of HOTUpdates