From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: lcj122@163.com
Subject: 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 14:02:23 +0000
Message-ID: <17143-c8fc83cb45e831ab@postgresql.org> (raw)
The following bug has been logged on the website:
Bug reference: 17143
Logged by: lcj
Email address: lcj122@163.com
PostgreSQL version: 11.5
Operating system: liunx
Description:
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. Now using amcheck to check the index, we find that the same
index is no problem on the primary, but the standby is indeed damaged.
The error reported on the standby machine is as follows:
ERROR: item order invariant violated for index "xxxx"
DETAIL: Lower index tid=(965,50) (points to heap tid=(13502,8)) higher
index tid=(965,51) (points to heap tid=(40017,19)) page lsn=392/59A2C8.
Does anyone know the reason? thanks.
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: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, lcj122@163.com
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>
* 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