I mistyped and yes B101 is a replica node, not primary.
The correct architecture is
A101(primary) -> A201(replica) -> B101(replica) -> B201(replica)
On Mon, Oct 3, 2022 at 5:55 PM Michael Paquier wrote:
> On Mon, Oct 03, 2022 at 12:41:23PM -0700, John Bolliger wrote:
> > Our architecture is sim
On Mon, Oct 03, 2022 at 12:41:23PM -0700, John Bolliger wrote:
> Our architecture is similar but all of the servers are now on ZFS now and
> Postgres 13.8 with Ubuntu 18.04+ and still doing streaming replication, all
> with ECC memory and 26-64 cores with 192gb ram+ on top of a ZPOOL made out
> of
This is a follow up to
https://www.postgresql.org/message-id/CANQ55Tsoa6%3Dvk2YkeVUN7qO-2YdqJf_AMVQxqsVTYJm0qqQQuw%40mail.gmail.com,
which I am at the same company as the original poster.
Our architecture is similar but all of the servers are now on ZFS now and
Postgres 13.8 with Ubuntu 18.04+ and
On Fri, Jun 29, 2018 at 1:14 PM, Devin Christensen wrote:
>> From your description it sounds like it's happening in the middle of
>> streaming, right?
>
> Correct. None of the instances in the chain experience a crash. Most of the
> time I see the "incorrect re
> From your description it sounds like it's happening in the middle of
streaming, right?
Correct. None of the instances in the chain experience a crash. Most of the
time I see the "incorrect resource manager data checksum in record" error,
but I've also seen it manife
ar complaint that involves an ext4 primary and a btrfs replica:
https://dba.stackexchange.com/questions/116569/postgresql-docker-incorrect-resource-manager-data-checksum-in-record-at-46f-6
I'm having trouble imagining how the filesystem could be triggering a
problem though (unless ZoL is dramatically less st
I've been seeing this issue in multiple separate hot standby replication
chains of PostgreSQL servers (5 so far). There are 4 servers in each chain
(some running Ubuntu 14.04 and others Ubuntu 16.04. and PostgreSQL >= 10.1
and <= 11). We also have a mix of ext4 and zfs file systems. Here are the
de
