pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Christopher Browne <cbbrowne@acm.org>
To: pgsql-admin@postgresql.org
Subject: Re: When will my database crash?
Date: Wed, 08 Sep 2004 22:55:54 -0400
Message-ID: <m3llfkqhfp.fsf@wolfe.cbbrowne.com> (raw)
References: <20040908020214.M78932@eg-1.com>
	<NOEFLCFHBPDAFHEIPGBOEEBCCEAA.simon@2ndquadrant.com>

simon@2ndquadrant.com ("Simon Riggs") wrote:
> Proactive, planned maintenance is more manageable than sudden,
> grinding failure when you're at home in bed. Make sure your manager
> is part of the call-out plan, thats usually a good way to make them
> care about maintenance.

And regular maintenance allows "maintenance sessions" to become
individually _much_ less costly.  If the heavily-updated tables were
vacuumed daily or even hourly, it is quite likely that the issue would
go away, from whence comes the "pg_autovacuum" strategy.

> For most applications, you should be running VACUUM FULL at least
> monthly, since any more than that is effectively the same thing as
> "never", as your case shows.

So long as you vacuum heavily-updated tables often enough, run 'plain
VACUUM ANALYZE' once in a while, to catch the transaction ID rollover
issue, and have enough space in the free space map, VACUUM FULL
shouldn't be necessary.

At Afilias, we _never_ run VACUUM FULL in the production transactional
environment, or at least we haven't needed to since migrating to 7.4.
(On 7.2, we needed to do so periodically, as well as periodically
reindexing some tables.)
-- 
select 'cbbrowne' || '@' || 'ntlug.org';
http://www3.sympatico.ca/cbbrowne/sap.html
"A good system can't have a weak command language."  -- Alan Perlis
[This explains why MS-DOS and Windows can't possibly be good
systems...] 



view thread (5+ messages)

Message-ID: <m3llfkqhfp.fsf@wolfe.cbbrowne.com>
Permalink:  ../m3llfkqhfp.fsf@wolfe.cbbrowne.com/
Also on:    postgresql.org/message-id/m3llfkqhfp.fsf@wolfe.cbbrowne.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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: cbbrowne@acm.org
  Subject: Re: When will my database crash?
  In-Reply-To: <m3llfkqhfp.fsf@wolfe.cbbrowne.com>
  References: <20040908020214.M78932@eg-1.com> <NOEFLCFHBPDAFHEIPGBOEEBCCEAA.simon@2ndquadrant.com> <m3llfkqhfp.fsf@wolfe.cbbrowne.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