| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Craig Ringer <ringerc(at)ringerc(dot)id(dot)au> |
| Cc: | Anibal David Acosta <aa(at)devshock(dot)com>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Timeout error on pgstat |
| Date: | 2012-08-02 03:59:00 |
| Message-ID: | 9899.1343879940@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Craig Ringer <ringerc(at)ringerc(dot)id(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Anibal David Acosta | 2012-08-02 14:51:54 | Re: Timeout error on pgstat |
| Previous Message | Craig Ringer | 2012-08-02 02:00:41 | Re: Timeout error on pgstat |