Re: vacuum strategy

Tom Lane wrote:

>"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
>
>---------------------------(end of broadcast)---------------------------
>TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)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