Postgres Logical Replication and Idle Databases

OldestReplicationSlotLag Growing: This indicates that the replication slot used by DMS is not being consumed or advanced as expected In

The lag between primary and read replica exceeds 16 seconds without any heavy IOPS, sometimes 30 seconds I have spent a lot of effort on

oldest replication slot lag If the Postgres setting hot_standby_feedback is turned on, long-running transactions on the standby may prevent replication progress Check for any long-running

trucchi slot The BDR group replication slot is however inactive most of the time BDR maintains this slot and advances its LSN when all other peers have already consumed the