pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jim C. Nasby <jnasby@pervasive.com>
To: Chris Mckenzie <Chris.McKenzie@entrust.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Performance/Maintenance test result collection
Date: Wed, 17 May 2006 14:24:40 -0500
Message-ID: <20060517192440.GX26212@pervasive.com> (raw)
In-Reply-To: <DE02FD24E5A7504FA1D53631DA8CEA9BF8B6A3@sottmxs10.entrust.com>
References: <DE02FD24E5A7504FA1D53631DA8CEA9BF8B6A3@sottmxs10.entrust.com>

On Wed, May 17, 2006 at 01:50:22PM -0400, Chris Mckenzie wrote:
> Hi.
> 
> I'm trying to plan for a performance test session where a large database is
> subject to regular hits from my application while both regular and full
> database maintenance is being performed. The idea is to gain a better idea
> on the impact maintenance will have on regular usage, and when to reasonably
> schedule both regular and full maintenance.

What do you mean by "regular and full maintenance"? Do you mean VACUUM
FULL?

If you're vacuuming appropriately you shouldn't have any need to ever
VACUUM FULL...
-- 
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



view thread (4+ messages)  latest in thread

Message-ID: <20060517192440.GX26212@pervasive.com>
Permalink:  ../20060517192440.GX26212@pervasive.com/
Also on:    postgresql.org/message-id/20060517192440.GX26212@pervasive.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: jnasby@pervasive.com, Chris.McKenzie@entrust.com
  Subject: Re: Performance/Maintenance test result collection
  In-Reply-To: <20060517192440.GX26212@pervasive.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox