Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id 1839413A5D7F for ; Thu, 2 Aug 2012 11:52:12 -0300 (ADT) Received: from mail-yw0-f46.google.com ([209.85.213.46]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Swwl0-00066K-VC for pgsql-admin@postgresql.org; Thu, 02 Aug 2012 14:52:11 +0000 Received: by yhmm54 with SMTP id m54so8799019yhm.19 for ; Thu, 02 Aug 2012 07:51:58 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:x-mailer:thread-index:content-language :x-gm-message-state; bh=ly8cZukmOqotJkmCybK9bYAPSF3B3+WW8ViycYNpq7c=; b=az16Dbqacj0zaduxJetOcCUIr2BwYJ6hskkVApOvxPy2P8EvdjriDok/UkQ2H4QYNb Tf9+isa0Rteq5pfJOvlUc7VvlvtfOi6V4QToTr5+8dhS9gmQAkEQPykhQgmzi9UkddKx liIttxFy0kVn14Kdu3VrpeLTybwzhJZhO/PND4qvTQ1gIiz536E+IHMjy9mS2uGLU5Z3 ShrCg6zTa+QOJzWoPCtCAdRUzzOITy5wP6aKHWJUHwXkIlI7e6UAkaE+OMuEH0tY4C6u /1FSMjadiKg5gleV15r0fjBqIHCQjYbar2pgnyS0PoBBsxYJOzySnht/+6Liowes32zc n1EQ== Received: by 10.236.197.42 with SMTP id s30mr20884191yhn.64.1343919118191; Thu, 02 Aug 2012 07:51:58 -0700 (PDT) Received: from AnibalVAIO (host-1-86.b20.cvc.com.py. [186.2.211.86]) by mx.google.com with ESMTPS id w1sm5710068anm.8.2012.08.02.07.51.55 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 02 Aug 2012 07:51:57 -0700 (PDT) From: "Anibal David Acosta" To: "'Craig Ringer'" Cc: References: <00dc01cd7024$07854340$168fc9c0$@devshock.com> <5019DF49.9000408@ringerc.id.au> In-Reply-To: <5019DF49.9000408@ringerc.id.au> Subject: Re: Timeout error on pgstat Date: Thu, 2 Aug 2012 10:51:54 -0400 Message-ID: <005f01cd70be$5d7813a0$18683ae0$@devshock.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0060_01CD709C.D667AC20" X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQHVZjQZI4NQ5X/a022xRggIqRxt1gDkh7H9ly+GjMA= Content-Language: es-py X-Gm-Message-State: ALoCoQmFxdrwEz1lPcaXXCSS2v0ZA/nnD4v2eeTnVaYV6VOX7xmrtTu+CL3jRWKeREWE3hTEd1GI X-Pg-Spam-Score: -1.5 (-) X-Archive-Number: 201208/11 X-Sequence-Number: 39832 This is a multipart message in MIME format. ------=_NextPart_000_0060_01CD709C.D667AC20 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Craig, those lines appear between pgstat timeout ERROR: canceling autovacuum task CONTEXT: automatic vacuum of table "XXX" =20 The table XXX is a table with about 200 insert p/ second. No update or delete. =20 The problem apparently is just with this table because there are others autovacuum running and working fin over others tables =20 The only difference is that this table XXX has about 5millions of insert daily and all those 5millons are deleted in the night (cleanup process). =20 =20 =20 =20 De: Craig Ringer [mailto:ringerc@ringerc.id.au]=20 Enviado el: mi=E9rcoles, 01 de agosto de 2012 10:01 p.m. Para: Anibal David Acosta CC: pgsql-admin@postgresql.org Asunto: Re: [ADMIN] Timeout error on pgstat =20 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. =20 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 ------=_NextPart_000_0060_01CD709C.D667AC20 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Craig, those lines appear between pgstat timeout

ERROR:=A0 canceling autovacuum task

CONTEXT:=A0 automatic vacuum of table "XXX"<= /o:p>

 

The table XXX is a table with about 200 insert p/ secon= d. No update or delete.

 

The problem apparentl= y is just with this table because there are others autovacuum running and w= orking fin over others tables

 

The only differ= ence is that this table XXX has about 5millions =A0of insert daily and all = those 5millons are deleted in the night (cleanup process).

 

 

 

 

De: Craig Ringer [mailto:ringerc@ringerc.id.au]
Env= iado el: mi=E9rcoles, 01 de agosto de 2012 10:01 p.m.
Para: A= nibal David Acosta
CC: pgsql-admin@postgresql.org
Asunto: Re: [ADMIN] Timeout error on pgstat

 

On 08/02/2= 012 04:27 AM, Anibal David Acosta wrote:

I have a lot (mayb= e 1 every 10 seconds) of this error WARNING:  pgstat wait timeout=

A quick search suggests t= his can be due to excessive I/O. However, this thread:

h= ttp://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.



Was there any context to= the `cancelling autovacuum task' message?

= 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 p= g_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

= ------=_NextPart_000_0060_01CD709C.D667AC20--