Re: unexpected result for wastedbytes query after vacuum full
От | Justin Pryzby |
---|---|
Тема | Re: unexpected result for wastedbytes query after vacuum full |
Дата | |
Msg-id | 20191206232849.GT2082@telsasoft.com обсуждение исходный текст |
Ответ на | unexpected result for wastedbytes query after vacuum full (Mike Schanne <mschanne@kns.com>) |
Ответы |
RE: unexpected result for wastedbytes query after vacuum full
|
Список | 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 по дате отправления: