Hi!
Thank you.
>When you use replication slots, it is very important to put in place a
>monitoring solution to check if too much WAL is retained, and note
>that there is nothing able to do that natively in core Postgres.
>There are however multiple ways to solve this problem, like a
>background worker (for the slot monitoring as well as optionally
>killing and/or dropping), a simple cron job or even check_postgres.
Where to find some sample how to implement this ?
I read from docs that slot cannot dropped if it is in use.
How to stop replication in this case.
Andrus.