From: Guillaume Cottenceau <gc@mnc.ch>
To: pgsql-performance@postgresql.org
Subject: perf pb solved only after pg_dump and restore
Date: 28 Aug 2006 10:14:52 +0200
Message-ID: <8764gd1dkz.fsf@meuh.mnc.lan> (raw)
Hi,
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].
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..
Thanks for any tips.
Ref:
[1] Processes were always showing one/some postmaster on SELECT,
a constant load of 1, and vmstat always showing activity in
IO blocks out (application generate all sort of typical
statements, some SELECT, UPDATE, INSERT either "directly" or
through stored procedures)
--
Guillaume Cottenceau
Create your personal SMS or WAP Service - visit http://mobilefriends.ch/
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: perf pb solved only after pg_dump and restore
In-Reply-To: <8764gd1dkz.fsf@meuh.mnc.lan>
* 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