Re: No vacuum for insert-only database? - Mailing list pgsql-performance

From Alvaro Herrera
Subject Re: No vacuum for insert-only database?
Date
Msg-id 20060313174135.GA16213@surnet.cl
Whole thread Raw
In response to Re: No vacuum for insert-only database?  ("Craig A. James" <cjames@modgraph-usa.com>)
Responses Re: No vacuum for insert-only database?
List pgsql-performance
Craig A. James 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?

Transaction ID wraparound will be a problem at a bit less than 2 billion
transactions.  So if you vacuum the table every 1 billion transactions
you are safe.  I suggest you read the "routine maintenance" section in
the docs; the wraparound issue is explained there.

--
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

pgsql-performance by date:

Previous
From: "Craig A. James"
Date:
Subject: Re: No vacuum for insert-only database?
Next
From: "andremachado"
Date:
Subject: firebird X postgresql 8.1.2 windows, performance comparison