Re: PITR on different hardware

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Rod Taylor <pg(at)rbt(dot)ca>
Cc: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PITR on different hardware
Date: 2005-09-06 20:53:07
Message-ID: 20464.1126039987@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Rod Taylor <pg(at)rbt(dot)ca> writes:
> Secondly, is PostgreSQL smart enough to complain in these cases or will
> it be silent and cause unexpected data corruption later on?

It will catch anything that affects the contents or layout of
pg_control, which includes a fair amount of stuff (endianness,
most of the popular compile options, probably alignment). We
don't really guarantee to catch every possible incompatibility,
however.

> Can you go from Sparc on Solaris to Linux on AMD?

Almost certainly not --- aren't they different endianness?

> How about from UltraSparc IV to UltraSparc III?

Damifino. How much difference is there between those architectures?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim C. Nasby 2005-09-06 20:58:28 Re: Remove xmin and cmin from frozen tuples
Previous Message David Fetter 2005-09-06 20:49:28 Re: uuid type for postgres