John Sidney-Woollett wrote:
I've got a 7.4.6 db running on linux where we've been vacuuming full
the database each night, and have recently switched to vacuum analyse
instead.
We keep seeing this message at the end of the vacuum run:
WARNING: some databases have not been vacuumed in 2013308218
Ah.., no we're not vacuuming template0 or 1.
I didn't realise that the transaction ID would be stored here - I
assumed that they'd be in our database.
Do I need to need to (plain) vacuum, or vacuum full these template0 and
template1? And is this something that can be done once a week rather
John Sidney-Woollett wrote:
Ah.., no we're not vacuuming template0 or 1.
I didn't realise that the transaction ID would be stored here - I
assumed that they'd be in our database.
Do I need to need to (plain) vacuum, or vacuum full these template0 and
template1? And is this something that can be
Thanks Richard, I found the page too...
However the implication (and my confusion) is that you need to vacuum
your own databases only. It's not clear (to me) that you have to do the
same for template0 and template1 as well.
Perhaps when someone is updating the docs, something more explicit than
I've just noticed that the v8 docs are MUCH better in explaining this
than the 7.4.6 docs that I'm using (since I'm using 7.4.6 in production).
Perhaps if the same texts
QUOTE
play=# VACUUM;
WARNING: some databases have not been vacuumed in 1613770184 transactions
HINT: Better vacuum them
(Apologies if this message comes twice - my imap server and mail client
had a little problem)...
I've just noticed that the v8 docs are MUCH better in explaining this
than the 7.4.6 docs that I'm using (since I'm using 7.4.6 in production).
Perhaps if the same texts
QUOTE
play=# VACUUM;
John Sidney-Woollett [EMAIL PROTECTED] writes:
However the implication (and my confusion) is that you need to vacuum
your own databases only. It's not clear (to me) that you have to do the
same for template0 and template1 as well.
You have to vacuum template1, but not template0 because the
Thanks Tom, I figured it out after I saw the error message when trying
to vacuum template0.
I think the 7.4.x docs could do with a more explanation.
The 8.0 docs are better although a more explicit explanation stating
that you MUST vacuum analyze template1 (periodically) would be useful.
I've got a 7.4.6 db running on linux where we've been vacuuming full
the database each night, and have recently switched to vacuum analyse
instead.
We keep seeing this message at the end of the vacuum run:
WARNING: some databases have not been vacuumed in 2013308218 transactions
HINT: Better
