SEO
vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
04-08-2008, 07:32 PM
| ||||
| ||||
 vacuum confusion 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 vacuum them within 134175429 transactions, or you may have a wraparound failure. VACUUM Why are we seeing this message when the only databases in this cluster is the one we are vacuuming (each night), and template0 and template1? Is there something that we're not doing right? John Sidney-Woollett ---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org      |
|
04-08-2008, 07:33 PM
| ||||
| ||||
| Re: vacuum confusion 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. Thanks John Sidney-Woollett Tom Lane wrote: > John Sidney-Woollett <johnsw@wardbrook.com> 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 latter is > marked not datallowconn. Not sure if this is adequately explained > anywhere. The next-to-last para in section 21.1.3 does mention the > datallowconn exception, but perhaps doesn't spell it out well enough. > > regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match |
Linear Mode
