Re: Is any effect other process performance after vaccumdb finished ? - Mailing list pgsql-performance

From Craig Ringer
Subject Re: Is any effect other process performance after vaccumdb finished ?
Date
Msg-id 4DDF1B2F.4050708@postnewspapers.com.au
Whole thread Raw
In response to Is any effect other process performance after vaccumdb finished ?  (Junghwe Kim <junghwe.kim76@gmail.com>)
List pgsql-performance
On 27/05/2011 9:58 AM, Junghwe Kim wrote:
> Hi.
>
> First extremely thanks for your works about postgresql .
>
> I wonder that after executing 'vaccumdb  -z'  some other process can not
> read their own msg queue during 2 ~ 3 minuts.

The most likely cause is checkpoint activity. Enable checkpoint logging
and examine your server logs.

> vaccum executed every hour. and The processes have not any relations
> between postgreql.

Instead of running vacuum from cron or some other scheduler, turn on
autovacuum and set it to run aggressively. You will reduce the impact of
vacuum if you run it *often* (every few minutes if not more frequently)
and do so using autovacuum.

Best results will be had on PostgreSQL 8.4 or above.

Please read this if you need to follow up, so you include enough
information that a more complete answer can be given:

   http://wiki.postgresql.org/wiki/Guide_to_reporting_problems

--
Craig Ringer

Tech-related writing at http://soapyfrogs.blogspot.com/

pgsql-performance by date:

Previous
From: Junghwe Kim
Date:
Subject: Is any effect other process performance after vaccumdb finished ?
Next
From: Ivan Voras
Date:
Subject: Re: Performance block size.