Postgres Pro
Downloads
Home   >   mailing lists

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

From Robert Haas
Subject Re: Surprising dead_tuple_count from pgstattuple
Date
Msg-id AANLkTi=FHtpXd3abL402_1sPM=NaiYxLgA_6mv8VAdyY@mail.gmail.com
Whole thread Raw
In response to Re: Surprising dead_tuple_count from pgstattuple  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
Tree view 
On Mon, Aug 9, 2010 at 2:23 PM, Heikki Linnakangas
<heikki.linnakangas@enterprisedb.com> wrote:
> On 09/08/10 21:21, Robert Haas wrote:
>>
>> On Mon, Aug 9, 2010 at 1:50 PM, Simon Riggs<simon@2ndquadrant.com>  wrote:
>>>
>>> Any SQL statement that reads a block can do HOT pruning, if the block is
>>> otherwise unlocked.
>>
>> Where does heap_page_prune() get called from in the DELETE path?
>
> heapgetpage()

Ah, OK.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company

pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Surprising dead_tuple_count from pgstattuple
Next
From: Markus Wanner
Date:
Subject: Re: dynamically allocating chunks from shared memory