Thanks to visit codestin.com
Credit goes to postgrespro.com

Re: vacuum strategy - Mailing list pgsql-general

From Tom Lane
Subject Re: vacuum strategy
Date
Msg-id [email protected]
Whole thread Raw
In response to Re: vacuum strategy  ("scott.marlowe" <[email protected]>)
Responses Re: vacuum strategy
List pgsql-general
"scott.marlowe" <[email protected]> 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