pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ian Westmacott <ianw@intellivid.com>
To: pgsql-admin@postgresql.org
Subject: VACUUM and read-mostly tables
Date: Mon, 4 Apr 2005 23:58:13 -0400
Message-ID: <000201c53993$b07bb440$76d81e42@hsd1.ma.comcast.net> (raw)

I have a near-real-time system writing into a Postgres 7.4.2 database
on the order of 340 million rows per day in about 300 million
transactions.  So we quickly bump up against the XID wrap-around
issue.  To address this, we divide the tables into 24-hour periods.
Once we roll over to a new period, the old tables are read-mostly.
We then run vacuum every 24 hours.

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?

Thanks,

	--Ian




view thread (12+ messages)  latest in thread

Message-ID: <000201c53993$b07bb440$76d81e42@hsd1.ma.comcast.net>
Permalink:  ../000201c53993$b07bb440$76d81e42@hsd1.ma.comcast.net/
Also on:    postgresql.org/message-id/000201c53993$b07bb440$76d81e42@hsd1.ma.comcast.net

 · 

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

* 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