Re: Hot Standy introduced problem with query cancel behavior - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Hot Standy introduced problem with query cancel behavior
Date
Msg-id 23413.1262100174@sss.pgh.pa.us
Whole thread Raw
In response to Re: Hot Standy introduced problem with query cancel behavior  (Joachim Wieland <joe@mcknight.de>)
Responses Re: Hot Standy introduced problem with query cancel behavior  (Andres Freund <andres@anarazel.de>)
Re: Hot Standy introduced problem with query cancel behavior  (Joachim Wieland <joe@mcknight.de>)
List pgsql-hackers
Joachim Wieland <joe@mcknight.de> writes:
> If we use the same signal for both cases, the receiving backend cannot
> tell what the intention of the sending backend was. That's why I
> proposed to make SIGINT similar to SIGUSR1 where we write a reason to
> a shared memory structure first and then send the signal (see
> http://archives.postgresql.org/pgsql-hackers/2009-12/msg02067.php from
> a few days ago).

This seems like a fairly bad idea.  One of the intended use-cases is to
be able to manually "kill -INT" a misbehaving backend.  Assuming that
there will be valid info about the signal in shared memory will break
that.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: parse tree to XML format
Next
From: Tom Lane
Date:
Subject: Re: [PATCH] Provide rowcount for utility SELECTs