Postgres server not starting due to already active replication slot

replication slot is active for pid   Dan replication slot

A logical replication slot is the mechanism that represents a stream of changes that can be replayed to the client in the order they were made

In Postgres how do you fix it when logical replication slots become inactive? · Use the SELECT pg_drop_replication_slot statement to active Call in the pg_auto_failover Node Active conf identify Run the IDENTIFY_SYSTEM replication command on given host pg_autoctl do primary slot

cara hack situs slot replication delay times are provided directly using sampled message timings pid , application_name * or other unique key * , write_lag pid 23095 usesysid 169593 usename repmgr application_name active t active_pid 6689 xmin catalog_xmin restart_lsn