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

From Josh Berkus
Subject Re: Frequent Update Project: Design Overview of HOT Updates
Date
Msg-id 200611091321.21555.josh@agliodbs.com
Whole thread Raw
In response to Frequent Update Project: Design Overview of HOT Updates  ("Simon Riggs" <simon@2ndquadrant.com>)
Responses Re: Frequent Update Project: Design Overview of HOTUpdates  ("Simon Riggs" <simon@2ndquadrant.com>)
List pgsql-hackers
Simon,

> If we perform an update that meets the HOT criteria then we put the
> new version into the overflow relation; we describe this as a HOT
> UPDATE. If we perform an update that does not meet the criteria, then we
> carry on with the existing/old MVCC behaviour; we describe this as a
> non-HOT UPDATE.

Making the essential performance analysis question, "Am I HOT or Not?"  

Sorry, but someone had to say it.  ;-)

-- 
--Josh

Josh Berkus
PostgreSQL @ Sun
San Francisco


pgsql-hackers by date:

Previous
From: "Simon Riggs"
Date:
Subject: Re: Introducing an advanced Frequent Update Optimization
Next
From: Christopher Browne
Date:
Subject: Re: Introducing an advanced Frequent Update Optimization