Received: from localhost (unknown [200.46.204.191])
	by postgresql.org (Postfix) with ESMTP id 93E1F2E2EBB
	for <pgsql-sql-postgresql.org@postgresql.org>;
	Tue, 27 Nov 2007 18:06:33 -0400 (AST)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024)
	with ESMTP id 29321-03 for <pgsql-sql-postgresql.org@postgresql.org>;
	Tue, 27 Nov 2007 18:06:33 -0400 (AST)
Received: from 208091.vserver.de (nirs.de [62.75.208.91])
	by postgresql.org (Postfix) with ESMTP id 997092E2E8D
	for <pgsql-sql@postgresql.org>; Tue, 27 Nov 2007 18:06:32 -0400 (AST)
Received: from vista (p54AD26AD.dip0.t-ipconnect.de [84.173.38.173])
	by 208091.vserver.de (8.12.8/8.12.8) with ESMTP id lARM6UZB028671
	for <pgsql-sql@postgresql.org>; Tue, 27 Nov 2007 23:06:31 +0100
Reply-To: <pgsql@yukonho.de>
From: "Stefan Becker" <pgsql@yukonho.de>
To: <pgsql-sql@postgresql.org>
References: <474C78E2.400@fmed.uba.ar>
In-Reply-To: <474C78E2.400@fmed.uba.ar>
Subject: Re: pg_clog (?) problem with VACUMM
Date: Tue, 27 Nov 2007 23:05:44 +0100
Message-ID: <001d01c83141$a8a41520$f9ec3f60$@de>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcgxL39bdK3Ibb48Sxe7h+Uu8/wHCAAAEqOQ
Content-Language: de
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=0.024 tagged_above=0 required=5 tests=AWL=0.023,
	BAYES_50=0.001
X-Spam-Level: 
X-Archive-Number: 200711/136
X-Sequence-Number: 29664

Dear Gerardo and Pgsql-List,

>When executing a VACUUM, i have this msg:
>gse_new_version=# VACUUM ;
>ERROR:  could not access status of transaction 118
>DETAIL:  could not open file "pg_clog/0000": No existe el fichero o el

I had a similar problem.  I decided one day to "clean" out
The pg_clog/ directory of the database cluster.  These files'
"last modified time Stamps" on many files were quite 
old, so I deleted them.  This didn't have any consequences for
the data (dumps or indexes etc.) or the operation of 
the installation except, as I found out MUCH later found out
- I could no longer vacuum the Database.

I restored the missing files from a backup and everything
was okay again, after a vacuum of the database the
system cleaned out the older pg_log/ files on its own.

I hope you get things fixed!

My best regards,

Stefan Becker
Email: Stefan@yukonho.de