Received: from localhost (unknown [200.46.204.184]) by developer.postgresql.org (Postfix) with ESMTP id 918992E0032 for ; Fri, 25 Apr 2008 12:39:39 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 83692-02 for ; Fri, 25 Apr 2008 12:39:35 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.183]) by developer.postgresql.org (Postfix) with ESMTP id 23C102E003A for ; Fri, 25 Apr 2008 12:39:36 -0300 (ADT) Received: by wa-out-1112.google.com with SMTP id n7so6058252wag.5 for ; Fri, 25 Apr 2008 08:39:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=gzAlejEGY4QPsyRMkGxwtXI+Pm25qnktWcn5HhWhCFM=; b=UMumSxgWy+sy7Ogs85Mp1NfldRE28w+9A0r22SeXgYkyM8y2qZJXDhSejnQs4Bj2wcETCODSC5NI9LgzFjHESwWtjurXCNJ0UyMS9E6GHwqx8JeN7nsAAflMYIWE3fUz+xwH7x76DI/6m9fVIkrlkIomAG+qvnX0l7c6AzITUcg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=gTzkJj6NUsHin01eihNEiSdm+nU9Db+ZowkQmtjEbroIJ8jbEO0rgwxIPyIRatRf/ny4s19guyrxWAoM7icX0OKjcFsBUdKiKjOL7ki9Iye0eOeaCcBDxwbYfCHdDytT/pnDds+9sCyt1DP5w10nKHqIUur4wh+tZh2wkLwQ6tU= Received: by 10.114.159.1 with SMTP id h1mr3343463wae.147.1209137975263; Fri, 25 Apr 2008 08:39:35 -0700 (PDT) Received: by 10.115.111.4 with HTTP; Fri, 25 Apr 2008 08:39:35 -0700 (PDT) Message-ID: <4dd8f37f0804250839y5f2f49cdu9c813c73005cf32b@mail.gmail.com> Date: Fri, 25 Apr 2008 12:39:35 -0300 From: "=?ISO-8859-1?Q?M=E1rcio_Aguiar_Ribeiro?=" To: "Tom Lane" Subject: Re: Server format and recovery Cc: "Shane Ambler" , pgsql-admin@postgresql.org In-Reply-To: <19575.1209135082@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <4dd8f37f0804241817q4ac5da57t131f8f910f40209@mail.gmail.com> <4811E4C1.7000803@Sheeky.Biz> <19575.1209135082@sss.pgh.pa.us> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200804/254 X-Sequence-Number: 29018 Thanks for the fast response! The hardware was the same of the previous, but I'm not sure about Ubuntu version. As I got the whole old server backup, I know that the Postgres version is 8.2 by looking at the PGVERSION file. Not sure if it is 8.2.5, but I imagined that it wouldn't make much difference. I installed the postgres via apt-get, and the installation structure was the same of the previous one. I even tried to copy the whole Postgres installation from the backup, but when I try to start the server with the postgres command, I receive an error from the OS saying it was impossible to execute the binaries. Now I'm thinking that a 64bit version was installed. I'll try to investigate this a little further and keep up with you. Thanks for the help! On Fri, Apr 25, 2008 at 11:51 AM, Tom Lane wrote: > Shane Ambler writes: > > > M=E1rcio Aguiar Ribeiro wrote: > >> "FATAL: database files are incompatible with server > >> The database cluster was initialized with MAXALIGN 0, but the server > >> waas compiled with MAXALIGN 4." (translated from my language to > >> english by me) > > > > My first guess is that the new postgresql binaries are 64 bit but the > > old install was 32 bit. (I don't actually know the conditions for the > > MAXALIGN value) > > That's what I'm guessing too; see the previous report here: > > http://archives.postgresql.org/pgsql-admin/2007-12/msg00254.php > http://archives.postgresql.org/pgsql-admin/2008-01/msg00023.php > > The symptoms are a bit different (eg, large value instead of zero > for MAXALIGN) but that's not too surprising considering that 8.1 > and 8.2 have different sets of fields in pg_control. > > You'll need to get binaries that matched your originals and then > reinstall the database from your backup. > > regards, tom lane > --=20 Marcio Aguiar Ribeiro