Using PostgreSQL Logical Replication to Maintain an Always Up-to

Using PostgreSQL Logical Replication to Maintain an Always Up-to creation of replication slot failed 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 wild fury slot The dark side is that replication slots can cause disks to fill up with old WAL, killing the main production server In this article I explain

wild fury slot creating logical replication slots only on the primary Or in other words, logical slots are lost

avatar 777 slot 3 Scalability: When a Streaming Replication connection is created from a standby to a primary cluster, it connects into a Replication Slot, To resolve these errors, remove the used replication slots, or increase the value of the max_replication_slots parameter Resolution Remove used replication