Re: Suggestion: include interruption method for \watch option (page 1922, PostgreSQL 11.1 Documentation) - Mailing list pgsql-bugs

From Tom Lane
Subject Re: Suggestion: include interruption method for \watch option (page 1922, PostgreSQL 11.1 Documentation)
Date
Msg-id 17021.1548342192@sss.pgh.pa.us
Whole thread Raw
In response to Re: Suggestion: include interruption method for \watch option (page1922, PostgreSQL 11.1 Documentation)  (Francisco Olarte <folarte@peoplecall.com>)
Responses Re: Suggestion: include interruption method for \watch option (page1922, PostgreSQL 11.1 Documentation)  (Bruce Momjian <bruce@momjian.us>)
List pgsql-bugs
Francisco Olarte <folarte@peoplecall.com> writes:
> On Thu, Jan 24, 2019 at 10:33 AM <rodrigo_de_carlos@yahoo.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


pgsql-bugs by date:

Previous
From: José Almanzar
Date:
Subject: Help
Next
From: Thomas Munro
Date:
Subject: Re: BUG #15585: infinite DynamicSharedMemoryControlLock waiting inparallel query