Skip site navigation (1) Skip section navigation (2)

canceling autovacuum task error

From: tamanna madaan <tamanna(dot)madaan(at)globallogic(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: canceling autovacuum task error
Date: 2011-08-10 05:07:05
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-general
Hi All

I am using a cluster setup having postgres-8.4.0 and slon 2.0.4 is being
used for replication . It happened that the autovacuum was not running
successfully on one of the nodes in cluster and was giving error :

2011-05-13 23:07:42 CDTERROR:  canceling autovacuum task
2011-05-13 23:07:42 CDTCONTEXT:  automatic vacuum of table
2011-05-13 23:07:42 CDTERROR:  could not open relation with OID 141231 at
character 87

sometimes it was giving a different error as below :

2011-05-13 04:45:05 CDTERROR:  canceling autovacuum task
2011-05-13 04:45:05 CDTCONTEXT:  automatic analyze of table
2011-05-13 04:45:05 CDTLOG:  could not receive data from client: Connection
reset by peer
2011-05-13 04:45:05 CDTLOG:  unexpected EOF on client connection
2011-05-13 04:45:05 CDTERROR:  duplicate key value violates unique
constraint "sl_nodelock-pkey"
2011-05-13 04:45:05 CDTSTATEMENT:  select "_schemaname".cleanupNodelock();
insert into "_mswcluster".sl_nodelock values (    2, 0,

Can see the below log also in postgres logs :

"checkpoints are occurring too frequently (19 seconds apart)"
 I am not sure when these all errors started coming . Just noticed these
when database size grew huge and it became slow.

Can anybody shed some light on it if these errors are related or what could
be the reason for these errors .



pgsql-general by date

Next:From: c kDate: 2011-08-10 05:13:17
Subject: Re: [GENERAL] postgresql server crash on windows 7 when using plpython
Previous:From: Postgres UserDate: 2011-08-10 01:10:36
Subject: Re: Indicating DEFAULT values in INSERT statement

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group