| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(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 23:00:45 |
| Message-ID: | 1281394845.2142.1268.camel@ebony |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 2010-08-10 at 07:43 +0900, Itagaki Takahiro wrote:
> 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.
Good point. We should say "HOT updates" and "pruning" as separate
techniques. Itagaki invented the pruning technique and deserves much
credit for that.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Training and Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-08-09 23:17:48 | Re: dynamically allocating chunks from shared memory |
| Previous Message | Kevin Grittner | 2010-08-09 22:57:23 | Re: SHOW TABLES |