Re: pgstattuple: fix free space calculation - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pgstattuple: fix free space calculation
Date
Msg-id 2546121.1725741934@sss.pgh.pa.us
Whole thread Raw
In response to Re: pgstattuple: fix free space calculation  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
I wrote:
> Now alternatively you could argue that a "new" page isn't usable free
> space yet and so we should count it as zero, just as we don't count
> dead tuples as usable free space.  You need VACUUM to turn either of
> those things into real free space.  But that'd be a bigger definitional
> change, and I'm not sure we want it.  Thoughts?

On the third hand: the code in question is in statapprox_heap, which
is presumably meant to deliver numbers comparable to pgstat_heap.
And pgstat_heap takes no special care for "new" pages, it just applies
PageGetHeapFreeSpace (or PageGetExactFreeSpace after this patch).
So that leaves me feeling pretty strongly that this whole stanza
is wrong and we should just do PageGetExactFreeSpace here.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Undocumented functions
Next
From: David Rowley
Date:
Subject: Re: PostgreSQL 17 release announcement draft