>So in practice, should one vacuum template1 when
> vacuuming other database (Assuming one doesn't use vaccumdb
> script when vacuuming database)?
In practice, it shouldn't be a big deal to vacuum template1 once in a
while, because, since it shouldn't have much data other than
pg_catalog ta
>
> Yes: the wraparound limit is for transactions
> cluster-wide, not per
> database. If you make 1 change in template1 and then 2
> billion
> changes in some other databases, template1 is broken
> unless it's
> been vacuumed meanwhile.
>
> regards, tom lane
>
So in pr
Ludwig Isaac Lim <[EMAIL PROTECTED]> writes:
> Under normal circumstances, there's no need to vacuum
> template1 right?
Only if it hasn't been modified.
> Its quite difficult to imagine XID
> wraparound problems occuring in template1. I can't think
> how can 4 billion transactions occur in temp
Hi :
Saw this post on BUGS mailing list :
"Olleg Samoylov" writes:
>> Opps, template1 must not be vacuumed.
>Says who?
>If we didn't vacuum template1 then it would be subject to
>XID wraparound
>problems, unless it had never been modified, which is
>something vacuumdb
>can't count on.
> rega
