From: Guillaume Cottenceau <gc@mnc.ch>
To: Franck Routier <franck.routier@axege.com>
Cc: postgres performance list <pgsql-performance@postgresql.org>
Subject: Re: Postgresql performance degrading... how to diagnose the root cause
Date: Sat, 30 Mar 2013 01:02:55 +0100
Message-ID: <m3a9pleouo.fsf@mnc.ch> (raw)
In-Reply-To: <5155B3BB.4080209@axege.com>
References: <5155A33A.4090000@axege.com>
<m3hajudzv1.fsf@mnc.ch>
<5155B3BB.4080209@axege.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
Franck Routier <franck.routier 'at' axege.com> writes:
>> http://wiki.postgresql.org/wiki/Show_database_bloat
> How do I interpret the output of this query ? Is 1.1 bloat level on a
> table alarming, or quite ok ?
I am not very used to this, but I'd start by comparing the top
result in your established DB against the top result in your
fresh DB. What does it say? The wiki page says it is a loose
estimate, however, unusually larger tbloat and/or wastedbytes
might be an indication.
Of course, if you can afford it, a good old VACUUM FULL ANALYZE
VERBOSE would tell you how many pages were reclaimed while
rewriting the table. Otherwise, VACUUM VERBOSE on both the
established DB and a backup/restore on a fresh DB also provide a
helpful comparison of how many pages are used for suspected
tables.
--
Guillaume Cottenceau
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
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, franck.routier@axege.com
Subject: Re: Postgresql performance degrading... how to diagnose the root cause
In-Reply-To: <m3a9pleouo.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