Subscription produces a lot of replication slots - PostgreSQL

Subscription produces a lot of replication slots - PostgreSQL postgres drop replication slot Manage inactive or lagging replication slots​ Inactive or lagging replication could cause problems in a database, like an ever-increasing disk usage not postgres drop replication slot WARNING! Make sure to delete any replication slots if you stop using Materialize, or if either the Materialize or PostgreSQL instances crash To look up the

postgres drop replication slot In that case, the Azure Database for PostgreSQL flexible server instance automatically drops that unused logical replication slot That

postgresql replication slot A physical replication slot prevents a source DB instance from removing WAL data before it's consumed by all read replicas Each read replica has its own Postgresql during DELETE events, it is necessary to configure the replication identity of the tables Postgres offers 4 different types of REPLICA IDENTITY