Date: Tue, 2 May 2006 16:38:47 -0500
From: "Jim C. Nasby" <jnasby@pervasive.com>
To: Chris Mckenzie <Chris.McKenzie@entrust.com>
Cc: "'pgsql-performance@postgresql.org'" <pgsql-performance@postgresql.org>
Subject: Re: Postgres 7.4 and vacuum_cost_delay.
Message-ID: <20060502213847.GF97354@pervasive.com>
References: <DE02FD24E5A7504FA1D53631DA8CEA9BF8B614@sottmxs10.entrust.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <DE02FD24E5A7504FA1D53631DA8CEA9BF8B614@sottmxs10.entrust.com>
User-Agent: Mutt/1.5.11

show all and grep are your friend. From my laptop with 8.1:

decibel@phonebook.1[16:36]~:4%psql -tc 'show all' | grep vacuum_cost_delay|tr -s ' '
autovacuum_vacuum_cost_delay | -1 | Vacuum cost delay in milliseconds, for autovacuum.
vacuum_cost_delay | 0 | Vacuum cost delay in milliseconds.
decibel@phonebook.1[16:37]~:5%

I don't have a 7.4 copy around, but you can just check it yourself.

On Mon, May 01, 2006 at 02:40:41PM -0400, Chris Mckenzie wrote:
> Hi everyone.
> 
> I've got a quick and stupid question: Does Postgres 7.4 (7.x) support
> vacuum_cost_delay?
> 
> For all my googles and documentation reading I've determined it's not
> supported, only because I can't find a 7.x doc or forum post claiming
> otherwise.
> 
> Upgrading to 8.x is out of the question, but I still need to employ
> something to auto-vacuum a large and active database (possibly more than
> once a day) in a manner that wouldn't affect load at the wrong time.
> 
> If I could combine pg_autovacuum with vacuum_cost_delay I could potentially
> have a solution. (barring some performance testing)
> 
> The only problem with pg_autovacuum is the need for pg_statio, which itself
> will reduce performance at all times.
> 
> Any suggestions?
> 
> Thanks!
> 
> - Chris
> 
> 
> 

-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461