PostgreSQL Logical replication Practical use case

JDBC_00 ERROR: replication slot sdc is active for PID 22025 · Sign up · Login to the community · Scanning file for viruses · This file cannot

In this case the slot is called pg_basebackup_N where N is the PID of the backend process running the replication connection However there

replication slot postgres Currently postgres doesn't allow dropping a replication slot that's active This can make certain operations more time-consuming or stuck in production

replication slot already exists replication activity connection accepted events connection closed events Specifies a file location to store the process ID of the mongos process