PostgreSQL 16 Documentation: Streaming Replication Protocol

PostgreSQL 16 Documentation: Streaming Replication Protocol replication slot is active for pid And this finally explains why that inactive replication slot causes the retention of that much WAL on an idle database: there actually are some replication slot slot_name my_pub1 plugin pgoutput slot_type logical datoid 16401 database db temporary f active t active_pid

replication slot As mentioned earlier, each subscription receives changes from a replication slot on the remote side Additional table

replication slot already exists This command shows information about logical replication slots that are setup on the database It shows if the slot is active, the state of the WAL sender The logical replication slot “mylogslot” is also active and permanent It's client has received up to 0