| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | "Craig A(dot) James" <cjames(at)modgraph-usa(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: No vacuum for insert-only database? |
| Date: | 2006-03-13 17:41:35 |
| Message-ID: | 20060313174135.GA16213@surnet.cl |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | andremachado | 2006-03-13 18:11:54 | firebird X postgresql 8.1.2 windows, performance comparison |
| Previous Message | Craig A. James | 2006-03-13 17:19:32 | Re: No vacuum for insert-only database? |