Replication Slot size increasing rapidly for postgresql

When using asynchronous replication a failover can cause lost transactions Worst case failover time for primary failure is: loop_wait + primary_start_timeout +

replication slot ReplicationSlot [active=false, latestFlushedLsn=LSN Creation of replication slot failed connect

slot egt When using asynchronous replication a failover can cause lost transactions Worst case failover time for primary failure is: loop_wait + primary_start_timeout +

blood suckers 2 slot game This means that the connector is unable to report DDL change events back to consumers Logical decoding replication slots are supported on only primary servers