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
CFLAGS = "-Acpu=x86_64 -Amachine=x86_64"
Do we still need a dump/restore with this config?
Tom Lane wrote:
>=?ISO-8859-1?Q?Dirk_Lutzeb=E4ck?= <lutzeb(at)aeccom(dot)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
In response to
pgsql-admin by date
|Next:||From: FM||Date: 2005-07-19 19:49:41|
|Subject: PGSQL 7.4.8 : idle in transaction problem|
|Previous:||From: Ilja Golshtein||Date: 2005-07-19 17:24:27|
|Subject: Re: Old question - failed to find conversion function from|
pgsql-general by date
|Next:||From: Oisin Glynn||Date: 2005-07-19 18:01:38|
|Subject: Re: How to pass the password for login in psql|
|Previous:||From: Josef Springer||Date: 2005-07-19 17:26:30|
|Subject: How to pass the password for login in psql|