Robert Haas writes:
> 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.
Surely a bug ... please poke into it next time you see it.
regards, tom lane
On Sun, Oct 21, 2018 at 7:21 PM Tom Lane 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
Re: Tom Lane 2018-10-22 <80020.1540164...@sss.pgh.pa.us>
> * 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.
Fwiw, pgadmin4 is one of those. ^C do
I agree with your arguments, and if instead we put an option to disable
this before compiling or a set in the psql cli?
On Sun, Oct 21, 2018, 20:20 Tom Lane wrote:
> Renato dos Santos writes:
> > I have been using psql for quite a few days. And I have accidentally
> pressed the CTRL + \ keys th
Renato dos Santos writes:
> I have been using psql for quite a few days. And I have accidentally pressed
> the CTRL + \ keys that sends the signal QUIT+Coredump (CTRL+4 also sends the
> same signal).
> I hope it's relevant to more people. (This has bothered me.)
> this patch avoids the output o
