From: Andrew Sullivan <ajs@crankycanuck.ca>
To: pgsql-admin@postgresql.org
Subject: Re: How to monitor resources on Linux.
Date: Tue, 28 Aug 2007 16:28:54 -0400
Message-ID: <20070828202854.GB1983@phlogiston.dyndns.org> (raw)
In-Reply-To: <46D48211.8010806@the-allgoods.net>
References: <46D4353F.2040209@the-allgoods.net>
<815.1188324416@sss.pgh.pa.us>
<46D470D8.2030605@the-allgoods.net>
<20070828191143.GE13868@alvh.no-ip.org>
<46D47A13.3060907@the-allgoods.net>
<20070828195554.GB1683@phlogiston.dyndns.org>
<46D48211.8010806@the-allgoods.net>
On Tue, Aug 28, 2007 at 04:14:09PM -0400, John R Allgood wrote:
> We were running vacuum and vacuum full daily without the vaccum analyze
> on weekends. After about 2 weeks the master database would slow down.
That doesn't surprise me. If you have enough writes, the regular
vacuum isn't running often enough. The goal is to vacuum "just
enough". The vacuum delay stuff in more recent releases is valuable
here.
> How often do you run VACUUM or are you using the autovacumm daemon.
We have a complicated set of scripts that vacuum some tables very
often, some other tables less often, yet other tables rarely, and
some tables only once a week. Autovacuum is currently in final
testing, though, I believe (though it's not my department any more,
so liberal salting of my words is needed).
--
Andrew Sullivan | ajs@crankycanuck.ca
Everything that happens in the world happens at some place.
--Jane Jacobs
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-admin@postgresql.org
Cc: ajs@crankycanuck.ca
Subject: Re: How to monitor resources on Linux.
In-Reply-To: <20070828202854.GB1983@phlogiston.dyndns.org>
* 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