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

From Francisco Olarte
Subject Re: Suggestion: include interruption method for \watch option (page1922, PostgreSQL 11.1 Documentation)
Date
Msg-id CA+bJJby_BxDuGDxtYJbBRDsvvxatvpOCF8t2FN9Pof0SahiZKA@mail.gmail.com
Whole thread Raw
In response to Suggestion: include interruption method for \watch option (page 1922, PostgreSQL 11.1 Documentation)  (<rodrigo_de_carlos@yahoo.com>)
Responses Re: Suggestion: include interruption method for \watch option (page 1922, PostgreSQL 11.1 Documentation)
List pgsql-bugs
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.

I haven't read the relevant sources, but my bet is psql is catching
int in *ix to do that ( it does it for other things ).

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.

That ( knowing how to interrput things ) is not a programming, but a
basic OS - user issue.

Francisco Olarte.


pgsql-bugs by date:

Previous
From: Sergei Kornilov
Date:
Subject: Re: BUG #15585: infinite DynamicSharedMemoryControlLock waiting in parallel query
Next
From: PG Bug reporting form
Date:
Subject: BUG #15607: Automatic Database Backup shows status Failed