From: Markus Schaber <schabi@logix-tt.com>
To: Guillaume Cottenceau <gc@mnc.ch>
Cc: pgsql-performance@postgresql.org
Subject: Re: perf pb solved only after pg_dump and restore
Date: Mon, 28 Aug 2006 11:28:23 +0200
Message-ID: <44F2B737.7070301@logix-tt.com> (raw)
In-Reply-To: <8764gd1dkz.fsf@meuh.mnc.lan>
References: <8764gd1dkz.fsf@meuh.mnc.lan>
Hi, Guillaume
Guillaume Cottenceau wrote:
> We noticed a slowdown on our application while traffic was kinda
> heavy. The logics after reading the docs commanded us to trim the
> enlarged tables, run VACUUM ANALYZE and then expect fast
> performance again; but it wasn't the case[1].
What exactly do you mean with "trim the enlarged tables"?
> Out of the blue, we dumped the database, removed it, recreated
> from the restore, and now the performance is lightning fast
> again.
>
> Does it look familiar to anyone? I thought running VACUUM ANALYZE
> after a trim should be enough so that pg has assembled the data
> and has good statistical knowledge of the tables contents..
This looks like either your free_space_map setting is way to low, or you
have index bloat.
Maybe a VACUUM FULL fullowed by a REINDEX will have solved your problem.
It also might make sense to issue a CLUSTER instead (which combines the
effects of VACUUM FULL, REINDEX and physically reordering the data).
When the free_space_map is to low, VACUUM ANALYZE should have told you
via a warning (at least, if your logging is set appropriately).
HTH,
Markus
--
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf. | Software Development GIS
Fight against software patents in EU! www.ffii.org www.nosoftwarepatents.org
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: schabi@logix-tt.com, gc@mnc.ch
Subject: Re: perf pb solved only after pg_dump and restore
In-Reply-To: <44F2B737.7070301@logix-tt.com>
* 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