Re: Surprising dead_tuple_count from pgstattuple

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, 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 18:23:57
Message-ID: 4C6047BD.3050407@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 09/08/10 21:21, Robert Haas wrote:
> On Mon, Aug 9, 2010 at 1:50 PM, Simon Riggs<simon(at)2ndquadrant(dot)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()

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Markus Wanner 2010-08-09 18:28:24 Re: dynamically allocating chunks from shared memory
Previous Message Robert Haas 2010-08-09 18:21:45 Re: Surprising dead_tuple_count from pgstattuple