Restarting hot_standby replication when the *slave* fails Context: master-slave replication on Postgres 9.4, slave died a couple of weeks ago: 


the slave copied a WAL-File from the master, 
told the master that the file is copied, 
the master deleted the wal-file, 
the slave tried to play the corrupt wal-file,
found that the file is corrupt,
and gives up to start up. 


In the meantime the master have accumulated more logs than the database itself.

How can I tell master that the replication is over (to reconfigure the replication)? Any general comments how to proceed with this situation?
You must be using a replication slot.  It is causing the master to retain the log files, because it still thinks the replica will be needing them.  (That is the purpose of a replication slot).  Find the slot and delete it.  Then create a new one for the new replica you will need to seed.