Re: unexpected result for wastedbytes query after vacuum full - Mailing list pgsql-performance

From Jeff Janes
Subject Re: unexpected result for wastedbytes query after vacuum full
Date
Msg-id CAMkU=1zi58hnPahYjv=eNLuBoURA9HzKtrJ7TJZuxevc5yyycw@mail.gmail.com
Whole thread Raw
In response to Re: unexpected result for wastedbytes query after vacuum full  (Guillaume Lelarge <guillaume@lelarge.info>)
Responses Re: unexpected result for wastedbytes query after vacuum full  (Guillaume Lelarge <guillaume@lelarge.info>)
List pgsql-performance
On Tue, Dec 10, 2019 at 11:43 AM Guillaume Lelarge <guillaume@lelarge.info> wrote:

This query uses the column statistics to estimate bloat. AFAIK, json columns don't have statistics, so the estimation can't be relied on (for this specific table at least).

This was true prior to 9.5 (for xml at least, I don't know about json), but should not be true from that release onward.  But still the difference between 74440704 and 74506240, this does seem to me to be straining at a gnat to swallow a camel.

Cheers,

Jeff

pgsql-performance by date:

Previous
From: Guillaume Lelarge
Date:
Subject: Re: unexpected result for wastedbytes query after vacuum full
Next
From: Michael Lewis
Date:
Subject: Re: Specific query taking time to process