From: Jeremy Haile <jhaile@fastmail.fm>
To: Matthew T. O'Connor <matthew@zeut.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: Autoanalyze settings with zero scale factor
Date: Thu, 18 Jan 2007 15:21:47 -0500
Message-ID: <1169151707.6247.1169971737@webmail.messagingengine.com> (raw)
In-Reply-To: <45AFC86B.9010704@zeut.net>
References: <1169145474.20103.1169962769@webmail.messagingengine.com>
<45AFC86B.9010704@zeut.net>
> Unless it's just a bug, my only guess is that autovacuum may be getting
> busy at times (vacuuming large tables for example) and hasn't had a
> chance to even look at that table for a while, and by the time it gets
> to it, there have been tens of thousands of inserts. Does that sounds
> plausible?
Possible, but I think your next suggestion is more likely.
> Also, are other auto-vacuums and auto-analyzes showing up in the
> pg_stats table? Maybe it's a stats system issue.
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? Is there
anything I should watch to debug or monitor for this problem in the
future? I wish I'd noticed whether or not the stats collector process
was running before I restarted.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: jhaile@fastmail.fm, matthew@zeut.net
Subject: Re: Autoanalyze settings with zero scale factor
In-Reply-To: <1169151707.6247.1169971737@webmail.messagingengine.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox