pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bernhard D Rohrer <graylion@sm-wg.net>
Cc: pgsql-admin@postgresql.org
Subject: Re: pg recovery
Date: Wed, 02 Jan 2008 12:39:03 -0500
Message-ID: <17137.1199295543@sss.pgh.pa.us> (raw)
In-Reply-To: <477B5D58.2010409@sm-wg.net>
References: <4778D3AC.7080108@sm-wg.net>
	<6006.1199115273@sss.pgh.pa.us>
	<477B5D58.2010409@sm-wg.net>

Bernhard D Rohrer <graylion@sm-wg.net> writes:
> Tom Lane wrote:
>> I think you've got a cross-version problem, as in the database is really
>> PG 8.0 or earlier but you're trying to run 8.1 against it.  What is in
>> the PG_VERSION file?  Have you done "pg_resetxlog -f", and if so do you
>> have the original pg_control file to put back?

> as for the versions see for yourself:
> root@collab:/home/adminlion# cat /var/lib/postgresql/8.1/main/PG_VERSION
> 8.1
> root@collab:/home/adminlion# cat 
> /olddrive/var/lib/postgresql/8.1/main/PG_VERSION
> 8.1

Hmmm ... but it sure looks like the values are offset a few fields from
where they belong ... [ meditates awhile... ]  Ah, I've sussed it: the
pg_controldata output you showed can be explained exactly by the
assumption that this copy of pg_controldata thinks time_t is 64 bits
wide, where the pg_control file actually has 32-bit-wide time_t fields.
That explains both the ridiculously large dates (quite impossible for
32-bit time_t's) and the offsetting of the following fields.

So the short answer is probably that you're trying to use a 64-bit build
of Postgres against a 32-bit database.  You need to get a matching build.

(We really need to stop using time_t in pg_control.h ...)

			regards, tom lane



view thread (6+ messages)  latest in thread

Message-ID: <17137.1199295543@sss.pgh.pa.us>
Permalink:  ../17137.1199295543@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/17137.1199295543@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, graylion@sm-wg.net
  Subject: Re: pg recovery
  In-Reply-To: <17137.1199295543@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox