Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 4AA5A9FA356 for ; Thu, 1 Feb 2007 03:02:24 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-new, port 10024) with ESMTP id 95494-01 for ; Thu, 1 Feb 2007 03:02:12 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4 Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.224]) by postgresql.org (Postfix) with ESMTP id C043C9FB26A for ; Thu, 1 Feb 2007 03:02:13 -0400 (AST) Received: by nz-out-0506.google.com with SMTP id i11so430404nzh for ; Wed, 31 Jan 2007 23:02:12 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=dbuNjBPskFAzca7ioFYv/V0QaZhZnB2w5a0PHnyI+Pp80i87wWznNoLH5nN0iVPjnHj51NXcM37jXhb03/YtpGxM4vDgJc+iKOAKhz5+0qdicul/j8nEU2gysW8DWY00S1bWDbb+PaTzRSofDAwW0vPbQB2tqNqgtuhB05lwAfU= Received: by 10.64.131.4 with SMTP id e4mr3171534qbd.1170313332710; Wed, 31 Jan 2007 23:02:12 -0800 (PST) Received: by 10.65.206.17 with HTTP; Wed, 31 Jan 2007 23:02:12 -0800 (PST) Message-ID: Date: Thu, 1 Feb 2007 12:02:12 +0500 From: "Shoaib Mir" To: "Chris Hoover" Subject: Re: 8.1.3 Problem Cc: "pgsql-admin@postgresql.org" In-Reply-To: <1d219a6f0701311308n3c90bd1i1b7168b055f506d5@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_11399_23342780.1170313332673" References: <1d219a6f0701311308n3c90bd1i1b7168b055f506d5@mail.gmail.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200702/1 X-Sequence-Number: 24466 ------=_Part_11399_23342780.1170313332673 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline It looks like to be a data corruption case.... a few cases like this have been discussed in the past as well. The following link --> http://archives.postgresql.org/pgsql-general/2006-12/msg01546.php might help you resolve the problem. -------------- Shoaib Mir EnterpriseDB (www.enterprisedb.com) On 2/1/07, Chris Hoover wrote: > > I am starting to have some significant problems with one of my 8.1.3databases. I am getting more and more of these errors: > wbd,20552,dholton,2007-01-31 15:32:27.137 EST,45c0fcb4.5048,16,2007-01-31 > 15:31:48 EST,342126177,UPDATE,ERROR: could not access status of transaction > 253762136 > wbd,20552,dholton,2007-01-31 15:32:27.137 EST,45c0fcb4.5048,17,2007-01-31 > 15:31:48 EST,342126177,UPDATE,DETAIL: could not open file "pg_clog/00F2": > No such file or directory > > > This is happening more and more, and on seeming random databases. Any > idea what is going on? I have already dumped and reloaded 2-3 of my > databases and now have about 3 more suffering from this. > > Right now, I can't upgrade to 8.1.6 until around March (have to wait until > the current release of our application is released). I have 7 databases > running 8.1.3 (6 prod and 1 test/dev) and only the test/dev is exhibiting > this problem > > Any help/ideas on what is going on and how to fix would be appreciated. > > Chris > ------=_Part_11399_23342780.1170313332673 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline It looks like to be a data corruption case.... a few cases like this have been discussed in the past as well. The following link --> http://archives.postgresql.org/pgsql-general/2006-12/msg01546.php might help you resolve the problem.

--------------
Shoaib Mir
EnterpriseDB (www.enterprisedb.com)

On 2/1/07, Chris Hoover <revoohc@gmail.com> wrote:
I am starting to have some significant problems with one of my 8.1.3 databases.  I am getting more and more of these errors:
wbd,20552,dholton,2007-01-31 15:32:27.137 EST,45c0fcb4.5048,16,2007-01-31 15:31:48 EST,342126177,UPDATE,ERROR:  could not access status of transaction 253762136
wbd,20552,dholton,2007-01-31 15:32:27.137 EST,45c0fcb4.5048,17,2007-01-31 15:31:48 EST,342126177,UPDATE,DETAIL:  could not open file "pg_clog/00F2": No such file or directory


This is happening more and more, and on seeming random databases.  Any idea what is going on?  I have already dumped and reloaded 2-3 of my databases and now have about 3 more suffering from this.

Right now, I can't upgrade to 8.1.6 until around March (have to wait until the current release of our application is released).  I have 7 databases running 8.1.3 (6 prod and 1 test/dev) and only the test/dev is exhibiting this problem

Any help/ideas on what is going on and how to fix would be appreciated.

Chris

------=_Part_11399_23342780.1170313332673--