X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 896A456697 for ; Wed, 2 Mar 2005 13:40:53 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 63361-04 for ; Wed, 2 Mar 2005 13:40:51 +0000 (GMT) Received: from exchange.meridiascapital.com (atherton-ex-01.meridiascapital.net [65.90.55.78]) by svr1.postgresql.org (Postfix) with ESMTP id 4634F566A6 for ; Wed, 2 Mar 2005 13:40:43 +0000 (GMT) Received: from 192.168.19.2 ([192.168.19.2]) by atherton-ex-01.meridias.local ([192.168.8.78]) with Microsoft Exchange Server HTTP-DAV ; Wed, 2 Mar 2005 13:40:41 +0000 Received: from mail by atherton-ex-01.meridias.local; 02 Mar 2005 06:40:46 -0700 Subject: Re: Error when trying to do a recovery From: Warren Little To: Tom Lane Cc: pgsql-admin@postgresql.org In-Reply-To: <7689.1109744566@sss.pgh.pa.us> References: <1109712377.21580.39.camel@localhost.localdomain> <7689.1109744566@sss.pgh.pa.us> Content-Type: multipart/alternative; boundary="=-GTdSqvSUacXpjpxnxUyR" Date: Wed, 02 Mar 2005 06:40:46 -0700 Message-Id: <1109770846.3031.11.camel@mail> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 (2.0.2-3) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.093 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO, HTML_40_50, HTML_MESSAGE X-Spam-Level: X-Archive-Number: 200503/54 X-Sequence-Number: 16552 --=-GTdSqvSUacXpjpxnxUyR Content-Type: text/plain Content-Transfer-Encoding: 7bit Tom, Thanks for your response. I found an old thread you had responded to a while back regarding 32 vs 64 bit architectures (which I have) and compatibility issues. So until I upgrade my backup/test box looks like I'm stuck using pg_dump :( Thanks On Wed, 2005-03-02 at 01:22 -0500, Tom Lane wrote: > Warren Little writes: > > When I start postgres (pg_ctl -l logfile start). The following text is > > all that exists in the logfile: > > > <2005-03-01 14:21:43 MST>FATAL: incorrect checksum in control file > > > What control file is it referring to? > > $PGDATA/global/pg_control. I think this must mean that you are trying > to start a postmaster that is fundamentally incompatible with the old > postmaster --- enough so that it thinks the pg_control struct should be > a different size than the old postmaster thought. > > regards, tom lane --=-GTdSqvSUacXpjpxnxUyR Content-Type: text/html; charset=utf-8 Tom,
Thanks for your response.  I found an old thread you had responded to a while back
regarding 32 vs 64 bit architectures (which I have) and compatibility issues.
So until I upgrade my backup/test box looks like I'm stuck using pg_dump :(

Thanks


On Wed, 2005-03-02 at 01:22 -0500, Tom Lane wrote:
Warren Little <warren.little@meridiascapital.com> writes:
> When I start postgres (pg_ctl -l logfile start). The following text is
> all that exists in the logfile:

> <2005-03-01 14:21:43 MST>FATAL:  incorrect checksum in control file

> What control file is it referring to?

$PGDATA/global/pg_control.  I think this must mean that you are trying
to start a postmaster that is fundamentally incompatible with the old
postmaster --- enough so that it thinks the pg_control struct should be
a different size than the old postmaster thought.

			regards, tom lane
--=-GTdSqvSUacXpjpxnxUyR--