Re: Logical replication timeout problem

replication slot: FAILED lock was still there containing the supposedly PID that ran before the

ERROR: could not create replication slot localharvest: ERROR: logical decoding cannot be used while in recovery SELECT slot_name, slot_type, active

error slot error saying the replication slot is already in use Here is the Powered by Discourse, best viewed with JavaScript enabled

error_ replication slot is active for pid Now a common cause for this kind of issue are replication slots which are not advanced: in that case, Postgres will hold on to all WAL segments