I’ve migrated my pg cluster to the new postgres-flex stack (3 nodes for HA), now seeing some disconnects (none led to downtime, but some background jobs crashed)
in my pg logs
deadMemberMonitorTick failed with: no rows in result set
deadMemberMonitorTick failed with: no rows in result set
LOG: recovery restart point at 3/D0031548
DETAIL: Last completed transaction was at log time 2023-02-27 12:46:36.649855+00.
LOG: restartpoint starting: time
LOG: restartpoint complete: wrote 4 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.302 s, sync=0.002 s, total=0.305 s; sync files=3, longest=0.001 s, average=0.001 s; distance=1 kB, estimate=298 kB
LOG: recovery restart point at 3/D0031548
DETAIL: Last completed transaction was at log time 2023-02-27 12:46:47.894142+00.
LOG: PID 28254 in cancel request did not match any process
Starting machine
machine became reachable in 11.131316ms
LOG: PID 28253 in cancel request did not match any process
monitoring primary node "fdaa:" (ID: ) in normal state
Starting machine
LOG: PID 28257 in cancel request did not match any process
Starting machine
machine became reachable in 13.610528ms
LOG: PID 28258 in cancel request did not match any process
machine became reachable in 10.41391ms
LOG: restartpoint starting: time
...
Starting machine
Starting machine
LOG: PID 28259 in cancel request did not match any process
LOG: PID 7802 in cancel request did not match any process
machine became reachable in 25.858475ms
machine became reachable in 26.533053ms
etc
`