Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 1EAA62E0080 for ; Tue, 3 Jun 2008 16:38:09 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 43175-08 for ; Tue, 3 Jun 2008 16:37:56 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mail.autorevenue.com (ip-208.178.167.106.gblx.net [208.178.167.106]) by developer.postgresql.org (Postfix) with ESMTP id 792802E003A for ; Tue, 3 Jun 2008 16:37:57 -0300 (ADT) Received: (qmail 9731 invoked from network); 3 Jun 2008 15:38:46 -0400 Received: from unknown (HELO dei26g028575) (msteben@10.10.1.20) by mail.autorevenue.com with SMTP; 3 Jun 2008 15:38:46 -0400 From: "Mark Steben" To: Subject: transaction status error Date: Tue, 3 Jun 2008 15:37:43 -0400 Message-ID: <002401c8c5b1$4b188300$14010a0a@dei26g028575> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0025_01C8C58F.C40BC500" X-Mailer: Microsoft Office Outlook 11 Thread-Index: AcjFsUrhkjrDJFWvTHWLkksLrHE8KA== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2992 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200806/20 X-Sequence-Number: 29358 This is a multi-part message in MIME format. ------=_NextPart_000_0025_01C8C58F.C40BC500 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi, I'm running 7.4.5 on a secondary remote database (running 8.2.5 everywhere else) This morning I was vacuuming template1 and the other databases on this machine. The postgres logs indicated that it removed a substantial number of commit logs, Presumably because they were obsolete: The message was: LOG: removing file "/var/lib/pgsql/data/pg_clog/07E7" Jun 3 09:37:59 supra postgres[19928]: [242-1] LOG: removing file "/var/lib/pgsql/data/pg_clog/0802" Jun 3 09:37:59 supra postgres[19928]: [243-1] LOG: removing file "/var/lib/pgsql/data/pg_clog/07E1" Jun 3 09:37:59 supra postgres[19928]: [244-1] LOG: removing file "/var/lib/pgsql/data/pg_clog/07B7" It removed some 100 of these logs. A little later when I attempted to vacuum template0 I get the following error: ERROR: could not access status of transaction 2065424697 ] DETAIL: could not open file "/var/lib/pgsql/data/pg_clog/07B1": No such file or directory Pointing to a commit log that had indeed been removed. The end result: As far as I can tell, I have access to all the databases, including template1, which I can copy from successfully in creating New databases. But The template0 database seems to be hosed. I can do a CREATE DATABASE from template0 but the new database Gets the same access status error. We are ok unless we access template0. And yes, we plan to upgrade to 8.x sometime next month. In the meantime, any ideas on how To fix this? Thank you, Mark Steben Senior Database Administrator @utoRevenueT A Dominion Enterprises Company 480 Pleasant Street Suite B200 Lee, MA 01238 413-243-4800 Home Office 413-243-4809 Corporate Fax msteben @autorevenue.com Visit our new website at www.autorevenue.com IMPORTANT: The information contained in this e-mail message is confidential and is intended only for the named addressee(s). If the reader of this e-mail message is not the intended recipient (or the individual responsible for the delivery of this e-mail message to the intended recipient), please be advised that any re-use, dissemination, distribution or copying of this e-mail message is prohibited. If you have received this e-mail message in error, please reply to the sender that you have received this e-mail message in error and then delete it. Thank you. ------=_NextPart_000_0025_01C8C58F.C40BC500 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi, I’m running 7.4.5 on a secondary remote database = (running 8.2.5 everywhere else)

  This morning I was vacuuming template1 and the other = databases on this machine.

 The postgres logs indicated that it removed a substantial = number of commit logs,

 Presumably because they were obsolete:  The message = was:

           = ;            =             &= nbsp;           &n= bsp;           &nb= sp;           &nbs= p; LOG:  removing file = "/var/lib/pgsql/data/pg_clog/07E7"

=

Jun  3 09:37:59 supra postgres[19928]: [242-1] LOG:  = removing file = "/var/lib/pgsql/data/pg_clog/0802"

=

Jun  3 09:37:59 supra postgres[19928]: [243-1] LOG:  = removing file = "/var/lib/pgsql/data/pg_clog/07E1"

=

Jun  3 09:37:59 supra postgres[19928]: [244-1] LOG:  = removing file = "/var/lib/pgsql/data/pg_clog/07B7"

=

 

It removed some 100 of these logs.

 

A little later when I attempted to vacuum template0 I get the = following error:

  ERROR:  could not access status of transaction = 2065424697

] DETAIL:  could not open file "/var/lib/pgsql/data/pg_clog/07B1": No such file or = directory

 

Pointing to a commit log that had indeed been = removed.

 

The end result:  As far as I can tell, I have access to all = the databases, including template1, which I can copy from successfully in = creating

New databases.  But The template0 database seems to be = hosed. I can do a CREATE DATABASE from template0 but the new = database

Gets the same access status error.  =

 

We are ok  unless we access template0.  And yes, we = plan to upgrade to 8.x sometime next month.  In the meantime, any ideas on = how

To fix this?

 

Thank you,

 

 

Mark Steben

Senior Database Administrator
@utoRevenue™
A Dominion = Enterprises Company
480 = Pleasant Street
Suite = B200
Lee, MA 01238
413-243-4800 Home Office 
413-243-4809 Corporate Fax

msteben@autorevenue.com

Visit our = new website at
www.autorevenue.com

 

IMPORTANT: The information = contained in this e-mail message is confidential and is intended only for the named addressee(s). If the reader of this e-mail message is not the intended recipient (or the individual responsible for the delivery of this e-mail message to the intended recipient), please be advised that any re-use, dissemination, distribution or copying of this e-mail message is = prohibited.  If you have received this e-mail message in error, please reply to = the sender that you have received this e-mail message in error and then = delete it.  Thank you.

 

------=_NextPart_000_0025_01C8C58F.C40BC500--