This patch reenables pg_terminate_backend, allowing (superuser only, of
course) to terminate a backend. As taken from the discussion some weeks
earlier, SIGTERM seems to be used quite widely, without a report of
misbehaviour so while the code path is officially not too well tested,
in practice it's working ok and helpful.
pg_reload_conf is a client-side issued SIGHUP, shouldn't provoke too
much problems.
Regards,
Andreas