From: Guillaume Cottenceau <gc@mnc.ch>
To: pgsql-performance@postgresql.org
Subject: Show_database_bloat reliability? [was: Re: REINDEX not working for wastedspace]
Date: Wed, 21 Sep 2011 14:43:07 +0200
Message-ID: <m37h5283s4.fsf@mnc.ch> (raw)
In-Reply-To: <CAGoODpcBxGLyF=bY3_5opO4YckgJqFGwBxveU_cYsrXBbN4NgQ@mail.gmail.com>
References: <CAGoODpcBxGLyF=bY3_5opO4YckgJqFGwBxveU_cYsrXBbN4NgQ@mail.gmail.com>
AI Rumman <rummandba 'at' gmail.com> writes:
> Using the query http://wiki.postgresql.org/wiki/Show_database_bloat, I got the
Is this stuff to show database bloat reliable? After a VACUUM
FULL of the table reported as the top responsible of bloat,
performing the same request again still gives the same result
(still that table is the top responsible of bloat):
current_database | schemaname | tablename | tbloat | wastedbytes | iname | ibloat | wastedibytes
------------------+------------+-----------------------------------------+--------+-------------+------------------------------------------------------+--------+--------------
test | public | requests | 1.1 | 14565376 | requests_pkey | 0.4 | 0
test | public | requests | 1.1 | 14565376 | idx_whatever | 0.8 | 0
test | public | requests | 1.1 | 14565376 | idx_whatever2 | 0.6 | 0
...
A few investigations show that when tbloat is close to 1.0 then
it seems not reliable, otherwise it seems useful.
pg 8.4.7
--
Guillaume Cottenceau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: gc@mnc.ch
Subject: Re: Show_database_bloat reliability? [was: Re: REINDEX not working for wastedspace]
In-Reply-To: <m37h5283s4.fsf@mnc.ch>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox