Re: vacuum strategy - Mailing list pgsql-general

From Tom Lane
Subject Re: vacuum strategy
Date
Msg-id 5090.1038280886@sss.pgh.pa.us
Whole thread Raw
In response to Re: vacuum strategy  ("scott.marlowe" <scott.marlowe@ihs.com>)
Responses Re: vacuum strategy  ("scott.marlowe" <scott.marlowe@ihs.com>)
List pgsql-general
"scott.marlowe" <scott.marlowe@ihs.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

pgsql-general by date:

Previous
From: "CN"
Date:
Subject: Delete Order When Referential Integrity Is Active
Next
From: Stephan Szabo
Date:
Subject: Re: Delete Order When Referential Integrity Is Active