Date: Thu, 21 Jun 2007 16:07:32 -0400
From: Bill Moran <wmoran@collaborativefusion.com>
To: "Steven Flatt" <steven.flatt@gmail.com>
Cc: "Francisco Reyes" <lists@stringsutils.com>,
	pgsql-performance@postgresql.org
Subject: Re: Database-wide VACUUM ANALYZE
Message-Id: <20070621160732.58497e2b.wmoran@collaborativefusion.com>
In-Reply-To: <357fa7590706211236y2856ed96q5394b9302b9a528f@mail.gmail.com>
References: <357fa7590706211009w2ef6071fn83c5759db6be1e80@mail.gmail.com>
	<cone.1182452313.269532.11564.5001@35st.simplicato.com>
	<357fa7590706211236y2856ed96q5394b9302b9a528f@mail.gmail.com>
Organization: Collaborative Fusion
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

In response to "Steven Flatt" <steven.flatt@gmail.com>:

> On 6/21/07, Francisco Reyes <lists@stringsutils.com> wrote:
> >
> > Are you on FreeBSD by any chance?
> >
> > I think the FreeBSD port by default installs a script that does a daily
> > vacuum.
> 
> 
> Yes, FreeBSD.  Do you know what script that is?

/usr/local/etc/periodic/daily/502.pgsql

> And it does a db-wide
> VACUUM ANALYZE every day?!  That is certainly not necessary, and in fact,
> costly for us.

You can control it with knobs in /etc/periodic.conf (just like other
periodic job):
daily_pgsql_vacuum_enable="YES"
daily_pgsql_backup_enable="NO"

are the defaults.

> Hmmm... I wonder why this would just start now, three days ago.  Everything
> seemed to be normal for the last two weeks.

Someone alter /etc/periodic.conf?  Perhaps it's been running all along but
you never noticed it before now?

-- 
Bill Moran
Collaborative Fusion Inc.
http://people.collaborativefusion.com/~wmoran/

wmoran@collaborativefusion.com
Phone: 412-422-3463x4023