Justin Pasher <just...@newmediagateway.com> writes:
> As you can see, it is starting to approach the 2 billion mark. If I
> change the datallowconn setting to TRUE, connect to template0, then
> perform a VACUUM FREEZE, the age(datfrozenxid) goes way down (probably
> around the 3 million mark). However, over time (typically less than two
> weeks), the number slowly creeps higher and higher, until our custom
> monitoring software starts spitting out a warning/error that the
> database should be vacuumed soon.
Recommendation: fix that monitoring software to ignore databases with
datallowconn = false. They're not supposed to need vacuuming.
(autovacuum will process them anyway for safety's sake, but they're
not supposed to need it.)
regards, tom lane
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
