Hello,
I have run into yet again another situation where there was an
assumption that autovacuum was keeping up and it wasn't. It was caused
by autovacuum quitting because another process requested a lock.
In turn we received a ton of bloat on pg_attribute which caused all
kinds of other issues (as can be expected).
The more I run into it, the more it seems like autovacuum should behave
like vacuum, in that it gets precedence when it is running. First come,
first serve as they say.
Thoughts?
JD
--
Command Prompt, Inc. - http://www.commandprompt.com/ 509-416-6579
PostgreSQL Support, Training, Professional Services and Development
High Availability, Oracle Conversion, Postgres-XC, @cmdpromptinc
For my dreams of your image that blossoms a rose in the deeps of my heart. - W.B. Yeats