We have found two things that appear to resolve the problem -
* Using a more powerful EC2 instance. We can reproduce the issue with
a r7a.medium instance but not with a r7a.large EC2 instance.
* Changing the Postgres synchronous_commit parameter from "on" to
"off". We cannot reproduce the issue with synchronous_commit set to
"off".
What is running on the EC2 instance?:
1) The Postgres server.
2) The replication receiver.
3) Both.
We need help to understand this unexpected behaviour.
We are using Postgres 14.10.
Thanks,
Daniel McKenzie
--
Adrian Klaver
adrian.kla...@aklaver.com
