Re: BUG #17143: when the CPU is different, the index on the primary is ok but the index on the standby is damaged

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: lcj122(at)163(dot)com
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17143: when the CPU is different, the index on the primary is ok but the index on the standby is damaged
Date: 2021-08-13 15:07:19
Message-ID: 70753.1628867239@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> Hello, I have encountered a problem in building a primary and standby
> cluster using physical streaming replication on different CPU machines.
> We created the primary on the x86 machine, and created the standby on the
> arm machine.

You should not expect that to work. Physical replication requires
identical hardware architectures, not to mention mostly-the-same
operating system software. (The most usual gotcha for cross-system
replication is different locale sort orders.)

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message David Christensen 2021-08-13 21:46:47 Re: BUG #17141: SELECT LIMIT WITH TIES FOR UPDATE SKIP LOCKED returns wrong number of rows
Previous Message David G. Johnston 2021-08-13 15:04:38 Re: BUG #17143: when the CPU is different, the index on the primary is ok but the index on the standby is damaged