Re: vacuum strategy - Mailing list pgsql-general

From Tina Messmann
Subject Re: vacuum strategy
Date
Msg-id 3DE33737.50703@xinux.de
Whole thread Raw
In response to Re: vacuum strategy  ("scott.marlowe" <scott.marlowe@ihs.com>)
Responses Re: vacuum strategy  ("Shridhar Daithankar" <shridhar_daithankar@persistent.co.in>)
Re: vacuum strategy  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Tom Lane wrote:

>"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
>
>---------------------------(end of broadcast)---------------------------
>TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
>
>
dump question:
what means this exactly?
does this include the template1 database? So i have to vacuum the
tempate1 database too on a regular  basis to avoid the rolling over of
the transaction id?

regards
tina


pgsql-general by date:

Previous
From: Christoph Dalitz
Date:
Subject: ALTER TRIGGER DISABLE/ENABLE
Next
From: "Shridhar Daithankar"
Date:
Subject: Re: vacuum strategy