Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 11C722E00B9 for ; Wed, 4 Jun 2008 01:12:04 -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 91595-02-5 for ; Wed, 4 Jun 2008 01:11:44 -0300 (ADT) Received: from mx2.hub.org (mx2.hub.org [200.46.204.254]) by developer.postgresql.org (Postfix) with ESMTP id 4E6652E00BF for ; Wed, 4 Jun 2008 01:06:11 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mx2.hub.org (Postfix) with ESMTP id DE96012A6B58 for ; Wed, 4 Jun 2008 01:04:31 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id m5442k4e016377; Wed, 4 Jun 2008 00:02:46 -0400 (EDT) To: "Mark Steben" cc: pgsql-admin@postgresql.org Subject: Re: transaction status error In-reply-to: <002401c8c5b1$4b188300$14010a0a@dei26g028575> References: <002401c8c5b1$4b188300$14010a0a@dei26g028575> Comments: In-reply-to "Mark Steben" message dated "Tue, 03 Jun 2008 15:37:43 -0400" Date: Wed, 04 Jun 2008 00:02:46 -0400 Message-ID: <16374.1212552166@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200806/21 X-Sequence-Number: 29359 "Mark Steben" writes: > Hi, I'm running 7.4.5 on a secondary remote database That release is nearly four years old... > A little later when I attempted to vacuum template0 I get the following > error: > ERROR: could not access status of transaction 2065424697 The 7.4.6 release notes mention something about Repair possible failure to update hint bits on disk Under rare circumstances this oversight could lead to "could not access transaction status" failures, which qualifies it as a potential-data-loss bug. That was sufficiently long ago that I don't recall how rare the "rare circumstances" might be. But you aren't going to rouse any interest in investigating bugs in such an ancient release. If you care about your data, you are supposed to keep up on minor releases. regards, tom lane