Server instrumentation: pg_terminate_backend, pg_reload_conf

From: Andreas Pflug <pgadmin(at)pse-consulting(dot)de>
To: PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Subject: Server instrumentation: pg_terminate_backend, pg_reload_conf
Date: 2005-06-01 21:07:53
Message-ID: 429E23A9.5030905@pse-consulting.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

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

Attachment Content-Type Size
admin-backend.patch text/x-patch 6.0 KB

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2005-06-01 23:28:01 Re: [ADMIN] Config option log_statement
Previous Message Pavel Stehule 2005-06-01 20:33:29 patch - doc for execute into (really)