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

From Justin Pryzby
Subject Re: unexpected result for wastedbytes query after vacuum full
Date
Msg-id 20191206232849.GT2082@telsasoft.com
Whole thread Raw
In response to unexpected result for wastedbytes query after vacuum full  (Mike Schanne <mschanne@kns.com>)
Responses RE: unexpected result for wastedbytes query after vacuum full  (Mike Schanne <mschanne@kns.com>)
List pgsql-performance
On Fri, Dec 06, 2019 at 05:18:20PM +0000, Mike Schanne wrote:
> Hi all,
> 
> This question is somewhat related to my previous question:
> https://www.postgresql.org/message-id/0871fcf35ceb4caa8a2204ca9c38e330%40USEPRDEX1.corp.kns.com
> 
> I was attempting to measure the benefit of doing a VACUUM FULL on my database.  I was using the query found here:
> https://wiki.postgresql.org/wiki/Show_database_bloat
> 
> However, I got an unexpected result in that the "wastedbytes" value actually increased for some tables after doing
thevacuum.
 

> I was wondering if the fact that we use a json column could be interfering with the wastedbytes calculation.  Can
anyoneexplain how wastedbytes could increase from a vacuum?
 

Is it due to dropped columns, like Tom explained here ?
https://www.postgresql.org/message-id/18375.1520723971%40sss.pgh.pa.us



pgsql-performance by date:

Previous
From: Tim Cross
Date:
Subject: Re: Legal disclaimers on emails to this group
Next
From: Jeff Janes
Date:
Subject: Re: autovacuum locking question