Thread: Intel x64 vs AMD x64 pgdata
Hey folks, Asking here since it may deal with clever things such as alignment and or binary reps. I'm migrating from some opterons to some xeons (E5345) both are running x86_64. At first I figured I'd need to dump & load my data, which will be painful. But on a whim I made a test db on the opteron, copied it over (tar) and it fired up and worked fine on the xeon. Seeing the success of this, I took our PITR backup and restored it properly, and everything seems to be functioning correctly from my tests. Is there anything I should be weary of doing this? I'd figure any alignment or other issues would have bitten me in my testing or PG would simply refuse to start. btw, the version in question is 8.2.5 thanks guys! -- Jeff Trout <jeff@jefftrout.com> http://www.dellsmartexitin.com/ http://www.stuarthamm.net/
Jeff Trout <threshar@threshar.is-a-geek.com> writes:
> I'm migrating from some opterons to some xeons (E5345) both are
> running x86_64. At first I figured I'd need to dump & load my data,
> which will be painful. But on a whim I made a test db on the
> opteron, copied it over (tar) and it fired up and worked fine on the
> xeon. Seeing the success of this, I took our PITR backup and
> restored it properly, and everything seems to be functioning
> correctly from my tests.
Sure, those are the same architecture as far as PG is concerned.
regards, tom lane
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, 2 Nov 2007 08:40:46 -0400
Jeff Trout <threshar@threshar.is-a-geek.com> wrote:
> Hey folks,
>
> Asking here since it may deal with clever things such as alignment
> and or binary reps.
>
> I'm migrating from some opterons to some xeons (E5345) both are
> running x86_64. At first I figured I'd need to dump & load my data,
> which will be painful. But on a whim I made a test db on the
> opteron, copied it over (tar) and it fired up and worked fine on the
> xeon. Seeing the success of this, I took our PITR backup and
> restored it properly, and everything seems to be functioning
> correctly from my tests.
x86_64 is x86_64, regardless of intel or amd.
Joshua D. Drake
- --
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
PostgreSQL solutions since 1997 http://www.commandprompt.com/ UNIQUE NOT NULL
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHK08WATb/zqfZUUQRAtRcAKCoh0UqQJCfCbRltsfdqgaoPpa/SACePsRQ
t3/gNGb9/Lus6JaiVj3yhuA=
=6vs/
-----END PGP SIGNATURE-----
Joshua D. Drake wrote:
>
> x86_64 is x86_64, regardless of intel or amd.
Not exactly, ask kernel guys ;-). But for user space yes.
Zdenek
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sun, 04 Nov 2007 19:28:46 +0100
Zdenek Kotala <Zdenek.Kotala@Sun.COM> wrote:
> Joshua D. Drake wrote:
>
> >
> > x86_64 is x86_64, regardless of intel or amd.
>
> Not exactly, ask kernel guys ;-). But for user space yes.
For the context of the discussion...
Joshua D. Drake
>
> Zdenek
>
- --
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
PostgreSQL solutions since 1997 http://www.commandprompt.com/ UNIQUE NOT NULL
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHLhG8ATb/zqfZUUQRAgwhAKCbpUKHy+1s8M+spvDrv93Lvw3xUgCffCR6
waU+dYx+RWCRBQBjFGUjvL8=
=q9jd
-----END PGP SIGNATURE-----