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 39D22529DE; Tue, 19 Jul 2005 14:49:13 -0300 (ADT) 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 22910-04; Tue, 19 Jul 2005 17:49:04 +0000 (GMT) Received: from mail2.aeccom.com (port-212-202-101-158.static.qsc.de [212.202.101.158]) by svr1.postgresql.org (Postfix) with ESMTP id 9BB3952988; Tue, 19 Jul 2005 14:49:00 -0300 (ADT) Received: from [192.168.2.12] (port-83-236-156-26.static.qsc.de [83.236.156.26]) by mail2.aeccom.com (Postfix) with ESMTP id C36B269; Tue, 19 Jul 2005 19:48:59 +0200 (CEST) Message-ID: <42DD3D0B.5080101@aeccom.com> Date: Tue, 19 Jul 2005 19:48:59 +0200 From: =?ISO-8859-1?Q?Dirk_Lutzeb=E4ck?= Organization: AEC/communications GmbH User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tom Lane Cc: pgsql-admin@postgresql.org, pgsql-general@postgresql.org, sgeisler@aeccom.com Subject: Re: dump/restore needed when switching from 32bit to 64bit References: <42DCC1E9.2060300@aeccom.com> <23511.1121781943@sss.pgh.pa.us> In-Reply-To: <23511.1121781943@sss.pgh.pa.us> Content-Type: multipart/alternative; boundary="------------090003060708020703040607" X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.101 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO, HTML_30_40, HTML_MESSAGE, HTML_TITLE_EMPTY X-Spam-Level: X-Archive-Number: 200507/132 X-Sequence-Number: 18188 This is a multi-part message in MIME format. --------------090003060708020703040607 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Thanks Tom, we now stay with 32bit to allow backward compatibilty with XEON which is needed as a fail-over system. The question is which gcc cflags are best used with XEON and Opteron to achieve fail-over compatibility. This is what we used for postgresql 8.0.3: XEON, RHEL 3.0 AS: CFLAGS = "-mcpu=pentium4 -march=pentium4" Opteron 875, RHEL 3.0 AS, gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-42): CFLAGS = "-Acpu=x86_64 -Amachine=x86_64" Do we still need a dump/restore with this config? Regards, Dirk Tom Lane wrote: >=?ISO-8859-1?Q?Dirk_Lutzeb=E4ck?= writes: > > >>when have a 8.0.3 database running on a XEON machine. We want to replace >>it with an Opteron where postgresql is to be compiled with 64bit. Do we >>need a dump/restore or can we just start the db with the new compilation? >> >> > >I'd bet you need a dump/restore --- MAXALIGN is most likely different >on the two platforms. If it isn't, then maybe you could get away with >this, but it's definitely risky. > > regards, tom lane > > --------------090003060708020703040607 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Thanks Tom,

we now stay with 32bit to allow backward compatibilty with XEON which is needed as a fail-over system.

The question is which gcc cflags are best used with XEON and Opteron to achieve fail-over compatibility. This is what we used for postgresql 8.0.3:

XEON, RHEL 3.0 AS:
    CFLAGS = "-mcpu=pentium4 -march=pentium4"

Opteron 875, RHEL 3.0 AS,  gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-42):
    CFLAGS = "-Acpu=x86_64 -Amachine=x86_64"

Do we still need a dump/restore with this config?

Regards,

Dirk


Tom Lane wrote:
=?ISO-8859-1?Q?Dirk_Lutzeb=E4ck?= <lutzeb@aeccom.com> writes:
  
when have a 8.0.3 database running on a XEON machine. We want to replace 
it with an Opteron where postgresql is to be compiled with 64bit. Do we 
need a dump/restore or can we just start the db with the new compilation?
    

I'd bet you need a dump/restore --- MAXALIGN is most likely different
on the two platforms.  If it isn't, then maybe you could get away with
this, but it's definitely risky.

			regards, tom lane
  
--------------090003060708020703040607--