From: Bernhard D Rohrer <graylion@sm-wg.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: pg recovery
Date: Wed, 02 Jan 2008 18:31:14 +0000
Message-ID: <477BD872.8070405@sm-wg.net> (raw)
In-Reply-To: <17137.1199295543@sss.pgh.pa.us>
References: <4778D3AC.7080108@sm-wg.net>
<6006.1199115273@sss.pgh.pa.us>
<477B5D58.2010409@sm-wg.net>
<17137.1199295543@sss.pgh.pa.us>
Tom Lane wrote:
> 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
exactly - I am currently installing a 32bit dapper on a VM in order to
do the migration
thanks muchly :)
Bernhard
--
Graylion's Fetish & Fashion Store
Goth and Kinky Boots, Clothing and Jewellery
http://www.graylion.net
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: graylion@sm-wg.net, tgl@sss.pgh.pa.us
Subject: Re: pg recovery
In-Reply-To: <477BD872.8070405@sm-wg.net>
* 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