From: Tom Lane <tgl@sss.pgh.pa.us>
To: Craig Ringer <ringerc@ringerc.id.au>
Cc: Anibal David Acosta <aa@devshock.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Timeout error on pgstat
Date: Wed, 01 Aug 2012 23:59:00 -0400
Message-ID: <9899.1343879940@sss.pgh.pa.us> (raw)
In-Reply-To: <5019DF49.9000408@ringerc.id.au>
References: <00dc01cd7024$07854340$168fc9c0$@devshock.com>
<5019DF49.9000408@ringerc.id.au>
Craig Ringer <ringerc@ringerc.id.au> writes:
> 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.
Yeah, a lot of us are wondering that. In principle, only a ridiculously
high load could result in triggering this message, but some people can
reproduce it under what apparently isn't very high load. If we could
identify what's different about their setups, maybe we could figure out
what's going on.
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-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, ringerc@ringerc.id.au, aa@devshock.com
Subject: Re: Timeout error on pgstat
In-Reply-To: <9899.1343879940@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