Subscription produces a lot of replication slots - PostgreSQL

This issue occurs in PostgreSQL when a user attempts to create or manage replication slots without the necessary privileges

Each replication slot streams a sequence of changes from a single database, and each publication exists in only one database, so you need to create one or more

postgres replication slot A replication slot exists solely on the instance that created it, and PostgreSQL does not replicate it on the standby servers As a result, after a failover or

postgresql replication slot This is an example using wal2json A replication slot must be created on the PostgreSQL server SELECT * FROM