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

From Martijn van Oosterhout
Subject Re: Frequent Update Project: Design Overview of HOT Updates
Date
Msg-id 20061109174945.GC23352@svana.org
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
Nice idea, just one question:

On Thu, Nov 09, 2006 at 05:13:16PM +0000, Simon Riggs wrote:
> Behavioural Characteristics
> ---------------------------
>
> With HOT, it is easily possible that the chain of prior versions spans
> many blocks. The chain always starts with the block of the root tuple
> but possibly includes many overflow relation blocks.
>
> A SeqScan of a HOT table will turn into a large number of
> random accesses to the overflow relation, which could be considerably
> more expensive than sequential I/O. Clearly very large tables would not
> be able to be HOT enabled without additional cost, so we make HOT a
> table-level option: WITH (freqUPDATE = on)   [discuss...]

It seems to me that bitmap index scans will get these same
characteristics also, right? The bitmap scan will have to follow the
chain of any possibly matching tuple in any of the blocks that are in
the bitmap, right?

Have a ncie day,
--
Martijn van Oosterhout   <kleptog@svana.org>   http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.

pgsql-hackers by date:

Previous
From: "Simon Riggs"
Date:
Subject: Frequent Update Project: Design Overview of HOT Updates
Next
From: "Simon Riggs"
Date:
Subject: Re: Frequent Update Project: Design Overview of HOTUpdates