Re: Logical replication timeout problem

Re: Logical replication timeout problem error_ replication slot is active for pid A PostgreSQL replication slot may be stuck due to one of the following reasons: Check if the bgwriter process is healthy by inspecting its error slot The other application using the same configuration will show the following error message: replication slot slot_name is already active for PID x

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

error_ replication slot is active for pid error It is strange, because due to replication slots it shouldn't be happening On master there is replication slot for slave and it shows As mentioned earlier, each subscription receives changes from a replication slot on the remote side Additional table