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
Date: Fri, 13 Aug 2021 11:07:19 -0400
Message-ID: <70753.1628867239@sss.pgh.pa.us> (raw)
In-Reply-To: <17143-c8fc83cb45e831ab@postgresql.org>
References: <17143-c8fc83cb45e831ab@postgresql.org>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, lcj122@163.com, 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: <70753.1628867239@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox