Postgres Pro
Downloads
Home   >   mailing lists

Re: Surprising dead_tuple_count from pgstattuple - Mailing list pgsql-hackers

From Itagaki Takahiro
Subject Re: Surprising dead_tuple_count from pgstattuple
Date
Msg-id AANLkTinB3R=yi8R+L_1k8jRaVSh5Hhx0yPSE86YV=ty+@mail.gmail.com
Whole thread Raw
In response to Re: Surprising dead_tuple_count from pgstattuple  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Surprising dead_tuple_count from pgstattuple  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
Tree view 
2010/8/10 Simon Riggs <simon@2ndquadrant.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

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: SHOW TABLES
Next
From: "Kevin Grittner"
Date:
Subject: Re: SHOW TABLES