Re: heap_page_prune comments

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Jim Nasby <jim(at)nasby(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: heap_page_prune comments
Date: 2011-11-04 15:18:45
Message-ID: CA+TgmoYLBcUgqqdE=sMKwcf5ZCsSsrcPGO8fpjGBKv_TPKdv6w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Nov 4, 2011 at 10:46 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> Seems a little hackish, though: we'd be reporting an amount of
>> freespace that we've deliberately set to an incorrect value.  I'm
>> almost thinking we should report the freespace that's actually
>> available, on the theory that Bload Is Bad (TM).
>
> IIRC, this code is following the very longstanding precedent of
> RelationGetBufferForTuple.

I don't understand the analogy - that function isn't freeing any
space, just searching for a block that already has some. And it does
update the free space map if the free space map is found to be out of
date, whereas this function does not.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Marti Raudsepp 2011-11-04 16:46:07 Re: IDLE in transaction introspection
Previous Message Tom Lane 2011-11-04 15:13:33 Re: Show statistics target in \d+