Re: Surprising dead_tuple_count from pgstattuple

From: Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Gordon Shannon <gordo169(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Surprising dead_tuple_count from pgstattuple
Date: 2010-08-09 22:43:50
Message-ID: AANLkTinB3R=yi8R+L_1k8jRaVSh5Hhx0yPSE86YV=ty+@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2010/8/10 Simon Riggs <simon(at)2ndquadrant(dot)com>:
> Any SQL statement that reads a block can do HOT pruning, if the block is
> otherwise unlocked.

We use the term "HOT" for two features:
1. HOT updates: Avoiding index updates when keys are not modified.
2. HOT pruning: Removing tuple bodies, that works even for indexed tuples.

2 is the point of the case, but ambiguous "HOT" might confuse some people.

--
Itagaki Takahiro

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2010-08-09 22:57:23 Re: SHOW TABLES
Previous Message Bruce Momjian 2010-08-09 22:38:32 Re: SHOW TABLES