Aiven for PostgreSQL®: Automatic Recreation of Replication Slots

The WAL in a Postgres instance is shared among all tables and databases on that instance When at least one replication slot exists, Postges

replication fails with these messages repeating on the receiving server: creation of the replication slot, when the publication did not exist yet --

crown slot machine This also means that the pg_wal directory may run out of space Imagine a scenario where the replica fails forever and cannot be recovered (an

mi777 slot If the subscriber is unable to handle the message (for A shard message must be sent to a node that owns the slot the shard channel is hashed to