From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Francisco Olarte <folarte(at)peoplecall(dot)com> |
Cc: | rodrigo_de_carlos(at)yahoo(dot)com, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Suggestion: include interruption method for \watch option (page 1922, PostgreSQL 11.1 Documentation) |
Date: | 2019-01-24 15:03:12 |
Message-ID: | 17021.1548342192@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Francisco Olarte <folarte(at)peoplecall(dot)com> writes:
> On Thu, Jan 24, 2019 at 10:33 AM <rodrigo_de_carlos(at)yahoo(dot)com> wrote:
>> I used the \watch option in psql and couldn’t stop the loop until I found the way* using ctrl-c. I am new to programming, and perhaps using ctrl-c is standard practice, but in a future manual perhaps you should replace the text below ‘until interrupted’ with ‘until interrupted (using ctrl-c)’.
> Ctrl-C, AFAIK, sends the INT(errupt) signal in *ix, which normally
> stops looping things. That's the standard way to interrupt long
> running commands, send them the interrupt signal.
> IIRC windows does similar stuff, although I think Ctrl-break had to be
> used, but I haven't used it since the dawn of the century.
Yeah, the reason that the message doesn't already mention control-c
is that the interrupt signal varies depending on platform (also,
it's possible to remap it to some other key, on most platforms).
In the end we expect you to know that much about whatever environment
you're using.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2019-01-24 15:30:19 | Re: How duplicate values inserted into the primary key column of table and how to fix it |
Previous Message | Hellmuth Vargas | 2019-01-24 14:43:11 | Re: How duplicate values inserted into the primary key column of table and how to fix it |