From: Joshua D. Drake <jd@commandprompt.com>
To: mischa@ca.sophos.com
Cc: Andrew Sullivan <ajs@crankycanuck.ca>
Cc: pgsql-performance@postgresql.org
Subject: Re: vacuuming problems continued
Date: Tue, 06 Jun 2006 12:21:39 -0700
Message-ID: <4485D5C3.7010803@commandprompt.com> (raw)
In-Reply-To: <4485CECC.4040207@ca.sophos.com>
References: <92d3a4950606010454y67293765o56001e8996975b45@mail.gmail.com>
<20060605204151.GC7071@phlogiston.dyndns.org>
<4485CECC.4040207@ca.sophos.com>
Mischa Sandberg wrote:
> Andrew Sullivan wrote:
>> On Thu, Jun 01, 2006 at 01:54:08PM +0200, Antoine wrote:
>>> Hi,
>>> We just don't seem to be getting much benefit from autovacuum. Running
>>> a manual vacuum seems to still be doing a LOT, which suggests to me
>>> that I should either run a cron job and disable autovacuum, or just
>>> run a cron job on top of autovacuum.
>
> Don't know if this was covered in an earlier thread. Bear with me if so.
>
> I'm working with 7.4.8 and 8.0.3 systems, and pg_autovacuum does have
> some glitches ... in part solved by the integrated autovac in 8.1:
>
> - in our env, clients occasionally hit max_connections. This is a known
> and (sort of) desired pushback on load. However, that sometimes knocks
> pg_autovacuum out.
That is when you use:
superuser_reserved_connections
In the postgresql.conf
> - db server goes down for any reason: same problem.
I believe you can use
stats_reset_on_server_start = on
For that little problem.
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
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: jd@commandprompt.com, mischa@ca.sophos.com, ajs@crankycanuck.ca
Subject: Re: vacuuming problems continued
In-Reply-To: <4485D5C3.7010803@commandprompt.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