Postgres Pro
Downloads
Home   >   mailing lists

Re: BUG #17143: when the CPU is different, the index on the primary is ok but the index on the standby is damaged - Mailing list pgsql-bugs

From Tom Lane
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
Msg-id 70753.1628867239@sss.pgh.pa.us
Whole thread Raw
In response to BUG #17143: when the CPU is different, the index on the primary is ok but the index on the standby is damaged  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
Tree view 
PG Bug reporting form <noreply@postgresql.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

pgsql-bugs by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: BUG #17143: when the CPU is different, the index on the primary is ok but the index on the standby is damaged
Next
From: David Christensen
Date:
Subject: Re: BUG #17141: SELECT LIMIT WITH TIES FOR UPDATE SKIP LOCKED returns wrong number of rows