From: Tom Lane <tgl@sss.pgh.pa.us>
To: Josh Kupershmidt <schmiddy@gmail.com>
Cc: Chris <lists@deksai.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: stats collector suddenly causing lots of IO
Date: Fri, 16 Apr 2010 12:39:54 -0400
Message-ID: <11003.1271435994@sss.pgh.pa.us> (raw)
In-Reply-To: <10744.1271435146@sss.pgh.pa.us>
References: <20100413170105.GA29571@chris-laptop.a2hosting.com>
<25952.1271370711@sss.pgh.pa.us>
<20100416151900.GA3179@chris-laptop.a2hosting.com>
<9857.1271431787@sss.pgh.pa.us>
<i2y4ec1cf761004160854z3d040cffjc83da673f3dbf6dd@mail.gmail.com>
<10744.1271435146@sss.pgh.pa.us>
I wrote:
> So this *should* have resulted in the stats file shrinking. Did you
> happen to notice if it did, after you did this?
Oh, never mind that --- I can see that it did shrink, just from counting
the write() calls in the collector's strace. So what we have here is a
demonstration that the tabpurge mechanism does work for you, when it's
invoked. Which is further evidence that for some reason autovacuum is
not running for you.
What I'd suggest at this point is cranking up log_min_messages to DEBUG2
or so in postgresql.conf, restarting the postmaster, and keeping an eye
on the log to see if you can spot anything about why autovac isn't
working.
regards, tom lane
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: tgl@sss.pgh.pa.us, schmiddy@gmail.com, lists@deksai.com
Subject: Re: stats collector suddenly causing lots of IO
In-Reply-To: <11003.1271435994@sss.pgh.pa.us>
* 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