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

Re: autovacuum: could not access status of transaction

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org,Nichlas Löfdahl <crotalus(at)acc(dot)umu(dot)se>
Subject: Re: autovacuum: could not access status of transaction
Date: 2006-03-31 04:09:32
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Robert Treat wrote:
> On Tuesday 28 March 2006 14:21, Nichlas Löfdahl wrote:

> > I've been running a server with autovacuum enabled for quite a while now
> > (months) without problems. But recently the server slowed down  and after
> > investigation I found the following repeated error messsage in the log:
> >
> > LOG:  autovacuum: processing database "template0"
> > ERROR:  could not access status of transaction 3541181801
> > DETAIL:  could not open file "pg_clog/0D31": No such file or directory
> Sorry, I am not really of any help with this, however I am finding it odd that 
> this message is occuring while trying to process template0.  Have you fuddled 
> with your system catalogs to make template0 connectable? Else ISTM autovacuum 
> should never be trying to process template0.  Anyone else want to weigh in 
> here? 

Hmm ... all databases, including those marked not connectable, are
vacuumed eventually, even if it's only for doing a no-op VACUUM FREEZE.
Maybe the database had the datistemplate bit reset, then it was modified
and not frozen again before setting the datistemplate bit again.

While I don't see why anyone would modify template0, it's certainly

Another possibility is that there is data corruption, but I would think
that it would present in other ways as well.

> > I assume that the avac-process halts at this point which means no vacuum
> > and/or analyze for the other databases? Which would explain the slowdown.

Yup.  Autovacuum would detect that template0 is the database in most
need of an autovacuum processing, then fail and die.  Subsequent autovac
iterations would do the same.

> > What is the best way to proceed with this? Stop the postmaster, create a
> > zero-filled pg_clog/0D31 and restart?

Yeah, I'd do that and VACUUM FREEZE template0 right away.  What files
are actually in pg_clog anyway?

Alvaro Herrera                      
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

pgsql-hackers by date

Next:From: Philipp OttDate: 2006-03-31 08:05:06
Subject: Postgres Library natively available for Mac OSX Intel?
Previous:From: Tom LaneDate: 2006-03-31 04:07:22
Subject: Re: Additional current timestamp values

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