Re: vacuum strategy

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>
Cc: CSN <cool_screen_name90001(at)yahoo(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: vacuum strategy
Date: 2002-11-26 03:21:26
Message-ID: 5090.1038280886@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

"scott.marlowe" <scott(dot)marlowe(at)ihs(dot)com> writes:
> Also, full vacuums are required every so often to keep the transaction id
> from rolling over.

Not so; a plain vacuum is fine for that. The critical point is that
*every* table in *every* database has to be vacuumed (plain or full)
at least once every billion transactions or so.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Stephan Szabo 2002-11-26 03:23:57 Re: Delete Order When Referential Integrity Is Active
Previous Message CN 2002-11-26 02:57:39 Delete Order When Referential Integrity Is Active