crash: replication slot already exists #22 - supabaserealtime

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

A replication slot is a PostgreSQL feature that ensures the master server keeps the WAL logs required by replicas even when they are

error_ draggable element must have an item slot pid WHERE _type = 'logical'; slot_name On pg_stat_activity I see the logical replication worker of this table always active

error_ replication slot is active for pid replication slot started lagging