From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | chris(at)bitmead(dot)com |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: [HACKERS] psql problem |
Date: | 2000-02-17 03:30:28 |
Message-ID: | 13062.950758228@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Chris Bitmead <chrisb(at)nimrod(dot)itg(dot)telstra(dot)com(dot)au> writes:
> I was noticing that psql now exits on ctrl-C.
Ugh. So now, if you type control-C while a query is in progress,
you get a cancel request sent, as you intended. Type it a tenth of
a second too late, however, and you get booted out of psql instead.
I think this is lousy human engineering, even though I'm sure Peter
thought it was a good idea at the time. If we trap control-C we
should trap it all the time, not create a delay-dependent behavior.
> This is much better than the previous behaviour where it kinda got
> muddled up and you could destroy your database if a half-completed
> command was in its buffer.
What? Are you saying that control-C doesn't do a \r (reset the
query buffer)? That's probably true, and I agree that it should...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2000-02-17 03:34:02 | Re: [HACKERS] psql problem] |
Previous Message | Tom Lane | 2000-02-17 03:23:46 | Re: [HACKERS] ERROR: Unable to identify an operator '=' for types 'numeric' and 'float8' |