On Mon, 2021-10-11 at 00:12 +0530, Anil wrote:
> Please find the server log, if you can find something (due to some reasons
> not being able to get OS system log, will be shared soon).
Nothing to see.
Perhaps an ill-configured network component closes idle connection?
In that case, try keepaliv
Hello Team,
Is there a way to monitor the replication lag, where replica nodes are
configured through aws s3.
Is not in a synced replica setup where master node will push the wal files
to aws s3 and we are taking and replaying those wal files on a replica node.
-Pawan
On Mon, Oct 11, 2021 at 05:58:03PM +0530, Pawan Sharma wrote:
> Is there a way to monitor the replication lag, where replica nodes are
> configured through aws s3.
You can check it on replica, by issuing:
select now() - pg_last_xact_replay_timestamp();
and it will show you, more or less, what is
Hello Depesz,
Thanks for your quick response, let me give some overview of our cluster
setups. Actually we have a Patroni cluster running with one replica
(Replica 1) in the same data center with no data lag. whereas we have
configured one more replica(Replica 2) in a different data center
throu
