Why our PostgreSQL replicas couldn't remove WAL files?

A PostgreSQL replication slot may be stuck due to one of the following reasons: Check if the bgwriter process is healthy by inspecting its

DROP TABLE removes tables from the database Only the table owner, the schema owner, and superuser can drop a table To empty a table of rows without destroying

postgresql drop replication slot The concept of replication slots was introduced in PostgreSQL and was created to prevent a primary instance to delete WAL that a replica

postgresql create replication slot replication connection and delete the slot as a single operation