Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id 56358259DA8 for ; Wed, 1 Aug 2012 23:01:02 -0300 (ADT) Received: from mail-ob0-f174.google.com ([209.85.214.174]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Swkij-0003FG-ED for pgsql-admin@postgresql.org; Thu, 02 Aug 2012 02:01:02 +0000 Received: by obbuo13 with SMTP id uo13so13088763obb.19 for ; Wed, 01 Aug 2012 19:00:48 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:x-gm-message-state; bh=bV7Whl6GNaF3Idvn51GGqqaNYzYopGQE5FLL/0beSs8=; b=LgQA66XgVSiSXg//RJ3PQQxY1nkFlZB/tW96QwKUb9YYceXN8xWrOtzWTXT+ENukzw 6etM6N8AbqwRztI1/A1KMgGvch8Fj+/yJsQXQuaBWp4+jil9N3Qy3CPQwstkOpwjZTjm qzWau2culgeALFrjmmaHId9p8+LVEzl1dx6ttmuRJw2vhnLPAPlaOjf8LE8Bm9f0RlIF 5wCpoR0lCnfK+5b90RMQS4UIRKCbO3zxquHIgN/70SW7QGfIJWkpePyc0G5rYXG1o9yM NEL5ZpSC/NsdEDX2hHCZJXQDcqQgAXT4FHAIquKxVyGmwuWFCZx3J6NFIINg7p59/ew8 A/pA== Received: by 10.60.2.161 with SMTP id 1mr33118861oev.48.1343872847793; Wed, 01 Aug 2012 19:00:47 -0700 (PDT) Received: from ayaki.localdomain (office1.postnewspapers.com.au. [150.101.171.128]) by mx.google.com with ESMTPS id ql3sm4228146obc.17.2012.08.01.19.00.44 (version=SSLv3 cipher=OTHER); Wed, 01 Aug 2012 19:00:47 -0700 (PDT) Message-ID: <5019DF49.9000408@ringerc.id.au> Date: Thu, 02 Aug 2012 10:00:41 +0800 From: Craig Ringer User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120717 Thunderbird/14.0 MIME-Version: 1.0 To: Anibal David Acosta CC: pgsql-admin@postgresql.org Subject: Re: Timeout error on pgstat References: <00dc01cd7024$07854340$168fc9c0$@devshock.com> In-Reply-To: <00dc01cd7024$07854340$168fc9c0$@devshock.com> Content-Type: multipart/alternative; boundary="------------000003090702000208070301" X-Gm-Message-State: ALoCoQkQDel7Lx1gZacl6uCY8zL1ofb1cgyM8S222og1uG+owyIxtAUM81LntslyH9wlp62VN/s2 X-Pg-Spam-Score: -0.8 (/) X-Archive-Number: 201208/9 X-Sequence-Number: 39830 This is a multi-part message in MIME format. --------------000003090702000208070301 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 --------------000003090702000208070301 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
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
--------------000003090702000208070301--