Re: BUG #17698: On SIGTERM, psql terminates, but leaves the statement running - Mailing list pgsql-bugs

From Tristan Partin
Subject Re: BUG #17698: On SIGTERM, psql terminates, but leaves the statement running
Date
Msg-id CSSYXFI3JCDF.1RO2ES99IT2GH@c3po
Whole thread Raw
In response to Re: BUG #17698: On SIGTERM, psql terminates, but leaves the statement running  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-bugs
On Mon Jan 16, 2023 at 9:14 AM CST, Alvaro Herrera wrote:
> On 2022-Nov-25, PG Bug reporting form wrote:
>
> > Reproduction: start psql, launch a query that will take a while (I
> > used 'select pg_sleep(1234)'), then from another terminal do
> > "kill -TERM <pid of psql>".  Psql would be terminated, but query would
> > not be, and will keep running until TCP timeout kicks in and kills the
> > stale connection.
> >
> > SIGINT, on the other hand, will cause psql will terminate the current
> > statement.
> >
> > Perhaps psql could have a SIGTERM handler that does roughly what
> > SIGINT handler does before terminating the whole process, and would
> > cancel the current statement (if any)?
>
> Sure.  I doubt we want to wait until a reply to the cancel request is
> obtained, but we could have the sigterm handler at least send it before
> terminating.

I am currently working on a patch for this.

--
Tristan Partin
Neon (https://neon.tech)



pgsql-bugs by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: How to restore database without re-write database and tables owner by using postgres
Next
From: PG Bug reporting form
Date:
Subject: BUG #17938: could not open shared memory segment "/PostgreSQL.615216676": No such file or directory