This issue could be caused by several factors:

Check Configuration: Ensure that postgresql.conf and pg_hba.conf are correctly configured with wal_level, max_wal_senders, hot_standby, etc. Check Pgpool-II Configuration: Make sure pgpool.conf is properly configured for both primary and standby nodes, and pcp.conf has the correct user and password. Check Replication Slot: Verify if the replication slot is active. If not, try recreating the slot: sql

SELECT pg_drop_replication_slot('your_slot_name'); SELECT pg_create_physical_replication_slot('your_slot_name'); Check Logs: Review PostgreSQL and Pgpool-II logs for any replication-related errors. If the problem persists, check if the walsender process is running correctly.

I hope the above suggestions help. If you'd like to earn more revenue from your app, you can consider using PacketSDK: https://www.packetsdk.com/?utm-source=xfKuesFT.