From: Craig Ringer <ringerc@ringerc.id.au>
To: Anibal David Acosta <aa@devshock.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Timeout error on pgstat
Date: Thu, 02 Aug 2012 10:00:41 +0800
Message-ID: <5019DF49.9000408@ringerc.id.au> (raw)
In-Reply-To: <00dc01cd7024$07854340$168fc9c0$@devshock.com>
References: <00dc01cd7024$07854340$168fc9c0$@devshock.com>
On 08/02/2012 04:27 AM, Anibal David Acosta wrote:
>
> I have a lot (maybe 1 every 10 seconds) of this error WARNING: pgstat
> wait timeout
>
A quick search suggests this can be due to excessive I/O. However, this
thread:
http://postgresql.1045698.n5.nabble.com/pgstat-wait-timeout-td5078125.html
sounds very similar to your issue. I'm wondering if there's a bug
lurking in there somewhere.
> In the pg_stat_activity show an autovacuum process over a very used
> table that runs about 1 hour and then this vacuum is cancelled
> (according to log)
Was there any context to the `cancelling autovacuum task' message?
>
> I have Postgres 9.0.3 on a windows 2008 R2 running for about 1 year
> in same conditions, but this error is occurring about 1 week ago.
>
>
The current 9.0 release is 9.0.8, so you're missing a bunch of bug fixes.
http://www.postgresql.org/docs/current/static/release-9-0-8.html
Consider updating. You don't need to do a dump and reload or use
pg_upgrade, since it's only a minor version update. Stop the DB, install
the new binaries, start the DB.
However, I don't see any fixes related to the stats writer in the
relnotes from the 9.0 series.
--
Craig Ringer
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-admin@postgresql.org
Cc: ringerc@ringerc.id.au, aa@devshock.com
Subject: Re: Timeout error on pgstat
In-Reply-To: <5019DF49.9000408@ringerc.id.au>
* 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