Documentation: 16: Streaming Replication Protocol

Physical slots are created automatically based on replica hosts and used for data replication within the Managed Service for PostgreSQL cluster

A replication slot ensures that the WAL will not go away if the replica lags behind Without a replication slot, a primary will recycle its WAL as soon as it

postgres delete replication slot Replication slots are marked as 'inactive' when the replication client connected to the slot disconnects Inactive replication slots cause WAL files to be

postgres create replication slot Take Away The morale of the story? Don't leave your replication slots unattended! There shouldn't be any slots which are inactive for too long