Re: vacuuming problems continued

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: mischa(at)ca(dot)sophos(dot)com
Cc: Andrew Sullivan <ajs(at)crankycanuck(dot)ca>, pgsql-performance(at)postgresql(dot)org
Subject: Re: vacuuming problems continued
Date: 2006-06-06 19:21:39
Message-ID: 4485D5C3.7010803@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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/

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Mischa Sandberg 2006-06-06 19:38:09 Re: vacuuming problems continued
Previous Message Mischa Sandberg 2006-06-06 18:51:56 Re: vacuuming problems continued