Hi,
I'm having trouble making sense of the these two autovacuum log entries.
I'm running PostgreSQL 8.4.
[2014-05-22 04:56:43.486 EST] {537cf2c6.30f9} LOG: automatic vacuum of
table postgres.globaldicom.requests: index scans: 1
pages: 0 removed, 163600 remain
tuples: 5916
Nick Cabatoff nick.cabat...@gmail.com writes:
I'm having trouble making sense of the these two autovacuum log entries.
I'm running PostgreSQL 8.4.
8.4.what?
It'd probably be a good idea to monitor the counts in pg_stat_all_tables
for the troublesome table(s). I suspect there are a whole lot
Hi Tom,
Thanks for the quick reply. 8.4.9. No db crashes, in fact not even a
restart in May until the 28th. I don't believe any HOT updates were
occurring in that table: all updates modify one or more indexed fields
(update status from pending to done, or update to store a stack trace and
bump
On Fri, Jul 4, 2014 at 7:41 AM, Nick Cabatoff nick.cabat...@gmail.com wrote:
8.4.9.
This has been released in 2011, so you are missing 3 years worth of
bug fixes. It may be a good idea to first update to 8.4.21 before
trying to work more on that (consider as well an upgrade as 8.4 will
be EOL
We've been running 9.2 on our later branches for a while now. We're
overdue to bump the older branches to a later 8.4 though, you're right.
Thanks for the reminder.
On Thu, Jul 3, 2014 at 7:46 PM, Michael Paquier michael.paqu...@gmail.com
wrote:
On Fri, Jul 4, 2014 at 7:41 AM, Nick Cabatoff
