crash: replication slot already exists #22 - supabaserealtime

This option causes the command to wait if the slot is active until it becomes inactive, instead of the default behavior of raising an error BASE_BACKUP

Streaming replication has stopped: You get this error when streaming replication between the primary and replica instances breaks down In this case,

error_ replication slot is active for pid If that happens, Amazon RDS generates a replication error and begins recovery on the read replica Recovering a read replica using its replication slot is

error 1089 The logical replication slot “mylogslot” is also active and permanent It's client has received up to 0