Re: : Tracking Full Table Scans

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Venkat Balaji" <venkat(dot)balaji(at)verse(dot)in>
Cc: "PGSQL Performance" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: : Tracking Full Table Scans
Date: 2011-09-27 17:15:43
Message-ID: 4E81BE6F02000025000417EF@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Venkat Balaji <venkat(dot)balaji(at)verse(dot)in> wrote:

> I would like to know the difference between "n_tup_upd" and
> "n_tup_hot_upd".

A HOT update is used when none of the updated columns are used in an
index and there is room for the new tuple (version of the row) on
the same page as the old tuple. This is faster for a number of
reasons, and cleanup of the old tuple is a little different.

If you want the gory implementation details, take a look at this
file in the source tree:

src/backend/access/heap/README.HOT

-Kevin

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Craig Ringer 2011-09-28 00:37:15 Re: postgres constraint triggers
Previous Message Venkat Balaji 2011-09-27 16:42:03 Re: : Tracking Full Table Scans