pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruno Wolff III <bruno@wolff.to>
To: Craig A. James <cjames@modgraph-usa.com>
Cc: Alvaro Herrera <alvherre@commandprompt.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: No vacuum for insert-only database?
Date: Mon, 13 Mar 2006 12:52:08 -0600
Message-ID: <20060313185208.GA5558@wolff.to> (raw)
In-Reply-To: <4415A9A4.5020903@modgraph-usa.com>
References: <44158989.6020103@modgraph-usa.com>
	<20060313150949.GK8274@surnet.cl>
	<4415A9A4.5020903@modgraph-usa.com>

On Mon, Mar 13, 2006 at 09:19:32 -0800,
  "Craig A. James" <cjames@modgraph-usa.com> wrote:
> Alvaro Herrera wrote:
> >>If I only insert data into a table, never update or delete, then I should 
> >>never have to vacuum it.  Is that correct?
> >
> >You still need to vacuum eventually, to avoid transaction Id wraparound
> >issues.  But not as often.
> 
> Thanks.  Any suggestions for what "not as often" means?  For example, if my 
> database will never contain more than 10 million rows, is that a problem?  
> 100 million rows?  When does transaction ID wraparound become a problem?

I believe it is at billion (10^9).



view thread (6+ messages)  latest in thread

Message-ID: <20060313185208.GA5558@wolff.to>
Permalink:  ../20060313185208.GA5558@wolff.to/
Also on:    postgresql.org/message-id/20060313185208.GA5558@wolff.to

 · 

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: bruno@wolff.to, cjames@modgraph-usa.com, alvherre@commandprompt.com
  Subject: Re: No vacuum for insert-only database?
  In-Reply-To: <20060313185208.GA5558@wolff.to>

* 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