Re: Frequent Update Project: Design Overview of HOT Updates

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Frequent Update Project: Design Overview of HOT Updates
Date: 2006-11-09 21:21:21
Message-ID: 200611091321.21555.josh@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Christopher Browne 2006-11-09 21:47:22 Re: Introducing an advanced Frequent Update Optimization
Previous Message Simon Riggs 2006-11-09 18:05:22 Re: Introducing an advanced Frequent Update Optimization