Tom Lane wrote:
> Well, that's pretty interesting. What are your vacuuming arrangements
> for this installation? Could the drop in file size have coincided with
> VACUUM operations? Because the ultimate backstop against bloated stats
> files is pgstat_vacuum_tabstat(), which is run by VACUUM and arranges to
> clean out any entries that shouldn't be there anymore.
VACUUM and ANALYZE are done by autovacuum only, no cron jobs.
autovacuum_naptime is 30 seconds so it should make it to each database
every 10 minutes or so. Do you think that more aggressive vacuuming
would prevent future swelling of the stats file?
> It's sounding like what you had was just transient bloat, in which case
> it might be useful to inquire whether anything out-of-the-ordinary had
> been done to the database right before the excessive-CPU-usage problem
> started.
I don't believe that there was any unusual activity on the server, but I
have set up some more detailed logging to hopefully identify a pattern
if the problem resurfaces.
Thanks.
--
Benjamin Minshall <minshall@intellicon.biz>
Senior Developer -- Intellicon, Inc.
http://www.intellicon.biz
