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

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: BUG #17143: when the CPU is different, the index on the primary is ok but the index on the standby is damaged
Дата
Msg-id 70753.1628867239@sss.pgh.pa.us
обсуждение исходный текст
Ответ на 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>)
Список pgsql-bugs
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 по дате отправления:

Предыдущее
От: "David G. Johnston"
Дата:
Сообщение: Re: BUG #17143: when the CPU is different, the index on the primary is ok but the index on the standby is damaged
Следующее
От: David Christensen
Дата:
Сообщение: Re: BUG #17141: SELECT LIMIT WITH TIES FOR UPDATE SKIP LOCKED returns wrong number of rows