Received: from localhost (unknown [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 1CFF22E3278 for ; Wed, 2 Jan 2008 14:31:23 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 55699-10 for ; Wed, 2 Jan 2008 14:31:15 -0400 (AST) Received: from collab.sm-wg.net (collab.sm-wg.net [86.43.106.231]) by postgresql.org (Postfix) with ESMTP id 830ED2E3255 for ; Wed, 2 Jan 2008 14:31:16 -0400 (AST) Received: from collab.sm-wg.net (localhost [127.0.0.1]) by collab.sm-wg.net (Postfix) with ESMTP id C19352D15A3; Wed, 2 Jan 2008 18:31:14 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sm-wg.net; h=message-id: date:from:mime-version:to:cc:subject:references:in-reply-to: content-type:content-transfer-encoding; q=dns/txt; s=m1; bh=b9kS eIZ+lL2meUY5MokEXuhWQWg=; b=UNDqMUw1wiR0F+fhuLpOige+3ZAHb4wMNWCd ayq2mJKMe2690J7TgkZP9864mhpkTgaFbWUnpSn7XxshW6B93Lw5p9MMrrwLHNbu erKsJ2i1TTET4ilUGweq6syU5qII1vYvr1klbYdRA1SaVtQlSa9O3UBe63asspHh 7l5hp2M= Received: from [192.168.1.8] (unknown [192.168.1.8]) by collab.sm-wg.net (Postfix) with ESMTP id A79D82D1571; Wed, 2 Jan 2008 18:31:14 +0000 (GMT) Message-ID: <477BD872.8070405@sm-wg.net> Date: Wed, 02 Jan 2008 18:31:14 +0000 From: Bernhard D Rohrer User-Agent: Thunderbird 2.0.0.6 (X11/20071022) MIME-Version: 1.0 To: Tom Lane CC: pgsql-admin@postgresql.org Subject: Re: pg recovery References: <4778D3AC.7080108@sm-wg.net> <6006.1199115273@sss.pgh.pa.us> <477B5D58.2010409@sm-wg.net> <17137.1199295543@sss.pgh.pa.us> In-Reply-To: <17137.1199295543@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200801/27 X-Sequence-Number: 27801 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