pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ian Westmacott <ianw@intellivid.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: VACUUM and read-mostly tables
Date: Tue, 05 Apr 2005 02:42:00 -0400
Message-ID: <10364.1112683320@sss.pgh.pa.us> (raw)
In-Reply-To: <000201c53993$b07bb440$76d81e42@hsd1.ma.comcast.net>
References: <000201c53993$b07bb440$76d81e42@hsd1.ma.comcast.net>

"Ian Westmacott" <ianw@intellivid.com> writes:
> The problem is that we are writing rows every 1/15 second, 24x7.  There
> is no down time.  I'm wondering if there is any way to avoid vacuuming
> the old tables over and over.  The documentation seems to indicate that
> a full vacuum is needed to avoid XID wrap-around.  Can vacuum freeze
> help me?

VACUUM FULL isn't really relevant.  VACUUM FREEZE on a particular table
should "fix" that table permanently, as long as you don't make any more
changes to it.  Keep in mind though that you still have to vacuum the
system catalogs often enough to avoid wraparound in them.  The real risk
here is in overlooking any one table.  You should probably use some kind
of automated vacuum driver ... have you looked at pg_autovacuum?

I believe Fujitsu is looking into what it'd take to make a variant
Postgres with 64-bit XIDs.  This'd probably imply also expanding CIDs,
OIDs, and some other things, so the space penalty is not to be sneezed
at ... but it might be worth it for installations like yours.

			regards, tom lane



view thread (12+ messages)  latest in thread

Message-ID: <10364.1112683320@sss.pgh.pa.us>
Permalink:  ../10364.1112683320@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/10364.1112683320@sss.pgh.pa.us

 · 

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: tgl@sss.pgh.pa.us, ianw@intellivid.com
  Subject: Re: VACUUM and read-mostly tables
  In-Reply-To: <10364.1112683320@sss.pgh.pa.us>
  References: <000201c53993$b07bb440$76d81e42@hsd1.ma.comcast.net> <10364.1112683320@sss.pgh.pa.us>

* 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