From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
---|---|
To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Cc: | dastapov(at)gmail(dot)com |
Subject: | BUG #17698: On SIGTERM, psql terminates, but leaves the statement running |
Date: | 2022-11-25 18:01:40 |
Message-ID: | 17698-58a6ab8caec496b0@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 17698
Logged by: Dmitry Astapov
Email address: dastapov(at)gmail(dot)com
PostgreSQL version: 14.2
Operating system: CentOS 7
Description:
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)?
From | Date | Subject | |
---|---|---|---|
Next Message | Vik Fearing | 2022-11-25 23:19:23 | Re: Inaccurate documentation about identifiers |
Previous Message | Tom Lane | 2022-11-25 17:06:15 | Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands |