pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Anibal David Acosta <aa@devshock.com>
To: 'Craig Ringer' <ringerc@ringerc.id.au>
Cc: pgsql-admin@postgresql.org
Subject: Re: Timeout error on pgstat
Date: Thu, 2 Aug 2012 10:51:54 -0400
Message-ID: <005f01cd70be$5d7813a0$18683ae0$@devshock.com> (raw)
In-Reply-To: <5019DF49.9000408@ringerc.id.au>
References: <00dc01cd7024$07854340$168fc9c0$@devshock.com>
	<5019DF49.9000408@ringerc.id.au>

Craig, those lines appear between pgstat timeout

ERROR:  canceling autovacuum task

CONTEXT:  automatic vacuum of table "XXX"

 

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

 

The problem apparently is just with this table because there are others
autovacuum running and working fin over others tables

 

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).

 

 

 

 

De: Craig Ringer [mailto:ringerc@ringerc.id.au] 
Enviado el: miƩrcoles, 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

 

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

view thread (6+ messages)  latest in thread

Message-ID: <005f01cd70be$5d7813a0$18683ae0$@devshock.com>
Permalink:  ../005f01cd70be$5d7813a0$18683ae0$@devshock.com/
Also on:    postgresql.org/message-id/005f01cd70be$5d7813a0$18683ae0$@devshock.com

 · 

reply

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: aa@devshock.com, ringerc@ringerc.id.au
  Subject: Re: Timeout error on pgstat
  In-Reply-To: <005f01cd70be$5d7813a0$18683ae0$@devshock.com>

* 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