Thread: Logical replication troubles

Thread: Logical replication troubles creation of replication slot failed This means that the connector is unable to report DDL change events back to consumers Logical decoding replication slots are supported on only primary servers slayers inc slot This leads to a completely broken logical replication downstream We can create a fresh slot on the new primary and set up a

slayers inc slot If the slot is a logical slot that was created in a database other than the database the walsender is connected to, this command fails slot_name The name of

the rift slot soldi veri Caused by: DebeziumException: Failed to start replication stream at LSN{B9DD22FBF0}; when setting up multiple connectors for the same database Based on this I'd say you didn't have enough wal_keep_segments on the master, weren't using a replication slot, and either had