Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id 1E89C15C4CC7 for ; Thu, 2 Aug 2012 00:59:15 -0300 (ADT) Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1SwmZ8-000553-7l for pgsql-admin@postgresql.org; Thu, 02 Aug 2012 03:59:14 +0000 Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.5/8.14.5) with ESMTP id q723x0Ab009900; Wed, 1 Aug 2012 23:59:00 -0400 (EDT) From: Tom Lane To: Craig Ringer cc: Anibal David Acosta , pgsql-admin@postgresql.org Subject: Re: Timeout error on pgstat In-reply-to: <5019DF49.9000408@ringerc.id.au> References: <00dc01cd7024$07854340$168fc9c0$@devshock.com> <5019DF49.9000408@ringerc.id.au> Comments: In-reply-to Craig Ringer message dated "Thu, 02 Aug 2012 10:00:41 +0800" Date: Wed, 01 Aug 2012 23:59:00 -0400 Message-ID: <9899.1343879940@sss.pgh.pa.us> X-Pg-Spam-Score: -0.8 (/) X-Archive-Number: 201208/10 X-Sequence-Number: 39831 Craig Ringer 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