Re: Patch to avoid SIGQUIT accident

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: shazaum(at)gmail(dot)com, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Patch to avoid SIGQUIT accident
Date: 2018-11-20 15:00:47
Message-ID: CA+Tgmoan158yFzQx8utHPgpAuOLWNw-_gKYg-yRayCx0P3E86w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Oct 21, 2018 at 7:21 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> * SIGQUIT is a fairly well-known way to get out of an application when all
> else fails. People who aren't familiar with psql's exit commands might
> find it pretty unfriendly of us to block this off.

Also, sometimes psql gets into a state where it doesn't respond to ^C,
but ^\ still kills it. I don't know why that happens, but I've seen
it repeatedly.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2018-11-20 15:14:26 Re: mysql_fdw crash
Previous Message Robert Haas 2018-11-20 14:53:11 Re: Shared Memory: How to use SYSV rather than MMAP ?