Re: Server instrumentation: pg_terminate_backend, pg_reload_conf

From: Andreas Pflug <pgadmin(at)pse-consulting(dot)de>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: Server instrumentation: pg_terminate_backend, pg_reload_conf
Date: 2005-06-05 09:56:08
Message-ID: 42A2CC38.80804@pse-consulting.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Andreas Pflug 2005-06-05 10:09:08 Re: pg_starttime()
Previous Message Simon Riggs 2005-06-05 08:06:37 Re: WAL bypass for CTAS