How is logical replication supposed to work with Patroni?
How is logical replication supposed to work with Patroni?
Currently postgres doesn't allow dropping a replication slot that's active This can make certain operations more time-consuming or stuck in production
This occurs when PostgreSQL does not have a replication slot for the secondary by that name You may want to rerun the replication process on the secondary How Debezium stops streaming: ERROR: cannot advance replication slot to XXXXXXXXX, minimum is YYYYYYYY · What Debezium connector do you use and what version? · What
slot casino online indonesia @myazid then there's something really strange in your setup since the logs you provided says that the replication slot has been created, look The slot to be dropped must be inactive before it can be removed It is not possible to forcibly drop an active replication slot Change history PostgreSQL
