From: Tom Lane <tgl@sss.pgh.pa.us>
To: lcj122@163.com
cc: pgsql-bugs@lists.postgresql.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
In-reply-to: <17143-c8fc83cb45e831ab@postgresql.org>
References: <17143-c8fc83cb45e831ab@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Fri, 13 Aug 2021 14:02:23 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <70752.1628867239.1@sss.pgh.pa.us>
Date: Fri, 13 Aug 2021 11:07:19 -0400
Message-ID: <70753.1628867239@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/70753.1628867239%40sss.pgh.pa.us>
Precedence: bulk

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