Re: AutoVacuum_NapTime

From: George Sexton
Subject: Re: AutoVacuum_NapTime
Date: ,
Msg-id: 053801cab295$5df355e0$19da01a0$@com
(view: Whole thread, Raw)
In response to: Re: AutoVacuum_NapTime  (Tom Lane)
Responses: Re: AutoVacuum_NapTime  (Alvaro Herrera)
List: pgsql-performance

Tree view

AutoVacuum_NapTime  ("George Sexton", )
 Re: AutoVacuum_NapTime  (Tom Lane, )
  Re: AutoVacuum_NapTime  ("George Sexton", )
   Re: AutoVacuum_NapTime  (Alvaro Herrera, )

> -----Original Message-----
> From: Tom Lane [mailto:]
> Sent: Saturday, February 20, 2010 6:15 PM
> To: George Sexton
> Cc: 
> Subject: Re: [PERFORM] AutoVacuum_NapTime
> "George Sexton" <> writes:
> > I have a system with around 330 databases running PostgreSQL 8.4.2
> > What would the expected behavior be with AutoVacuum_NapTime set to
> the
> > default of 1m and autovacuum_workers set to 3?
> autovacuum_naptime is the cycle time for any one database, so you'd
> get an autovac worker launched every 60/330 seconds ...
>             regards, tom lane

Thanks. That's non-optimal for my usage. I'll change it.

Another question then. Say I set it to 720 minutes, which if I understand
things would see each db done twice per day.

If I'm cold starting the system, would it vacuum all 330 databases and then
wait 720 minutes and then do them all again, or would it distribute the
databases more or less evenly over the time period?

George Sexton
MH Software, Inc.
Voice: 303 438 9585

pgsql-performance by date:

From: "terry"
Subject: Re: can we optimize STACK_DEPTH_SLOP
From: Scott Carey
Subject: Re: SSD + RAID