From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | PostgreSQL Development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: [HACKERS] psql and Control-C |
Date: | 2000-02-17 20:25:22 |
Message-ID: | 200002172025.PAA26232@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Charset ISO-8859-1 unsupported, filtering to ASCII...]
> Some people have indicated that they don't like how psql currently handles
> Control-C if no query is in progress. I consider the behaviour of the
> shells desirable but, quite frankly, I don't know how to do it.
>
> For some reason a readline'd session always wants me to press one more key
> after Control-C before getting back to a clean prompt. A much bigger
> problem is that if I don't use/have readline then I don't see a way to
> preempt the fgets() call.
>
> So unless someone has a hint or wants to look at it, I could offer
> ignoring the signal altogether in interactive mode, and perhaps make it
> stop scripts in the other case. (Leaving the query cancelling as is, of
> course.)
>
> Actually, shouldn't a Ctrl-C in a script cancel the query *and* stop the
> script at all times?
Seems we can just ignore ^C if a query is not being run. Is that OK
with everyone. Looks easy to do.
--
Bruce Momjian | http://www.op.net/~candle
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
Attachment | Content-Type | Size |
---|---|---|
unknown_filename | text/plain | 0 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 2000-02-17 22:10:01 | Re: [HACKERS] PC Week PostgreSQL benchmark results posted online (fwd) |
Previous Message | Michael Meskes | 2000-02-17 19:44:05 | Re: [HACKERS] function question yet again |