Why our PostgreSQL replicas couldn't remove WAL files?

Why our PostgreSQL replicas couldn't remove WAL files? postgresql drop replication slot If due to network breakdown or some other error, PostgreSQL is unable to remove the slots, an error will be reported To proceed in this situation, the user postgresql drop replication slot PostgreSQL Hackers pgsql-hackerslistspostgresqlorg>

postgresql drop 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

postgresql replication slot three instances postgresql cluster Finally I found out this delete all data on the replica and pull it from the leader): root@my Replication Slot 탄생PostgreSQL에서 안정적인 Replication 유지를 위한 WAL 파일의 관리는 항상 어려운 문제였습니다 Standby Server의 연결이