Re: Server instrumentation: pg_terminate_backend, pg_reload_conf - Mailing list pgsql-patches

From Andreas Pflug
Subject Re: Server instrumentation: pg_terminate_backend, pg_reload_conf
Date
Msg-id 42A2CC38.80804@pse-consulting.de
Whole thread Raw
In response to Re: Server instrumentation: pg_terminate_backend, pg_reload_conf  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: Server instrumentation: pg_terminate_backend, pg_reload_conf
List pgsql-patches
Bruce Momjian wrote:
> Andreas Pflug wrote:
>
>>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
>>misbehavior so while the code path is officially not too well tested,
>>in practice it's working ok and helpful.
>
>
> I thought we had a discussion that the places we accept SIGTERM might be
> places that can exit if the postmaster is shutting down, but might not
> be places we can exit if the postmaster continues running, e.g. holding
> locks.  Have you checked all the places we honor SIGTERM to check that
> we are safe to exit?  I know Tom had concerns about that.

My patch is purely to enable a supervisor to issue a SIGTERM using a
pgsql client, instead of doing it from a server command line. It's not
meant to fix the underlying problems.

Regards,
Andreas

pgsql-patches by date:

Previous
From: Simon Riggs
Date:
Subject: Re: WAL bypass for CTAS
Next
From: Andreas Pflug
Date:
Subject: Re: pg_starttime()