"Jeremy Haile" <[EMAIL PROTECTED]> writes:
> No tables have been vacuumed or analyzed today. I had thought that this
> problem was due to my pg_autovacuum changes, but perhaps not. I
> restarted PostgreSQL (in production - yikes) About a minute after being
> restarted, the autovac process fired up.
> What could get PG in a state where autovac isn't running?
Um, are you sure it wasn't? The autovac process is not an always-there
thing, it quits after each pass and then the postmaster starts a new one
awhile later.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster
