From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | Leon Mergen <leon(at)solatis(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [GENERAL] Unable to get postgres running after long time no vacuum |
Date: | 2007-07-08 23:53:52 |
Message-ID: | 18723.1183938832@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Tom Lane wrote:
>> At least on my machine there doesn't seem to be a defined way to
>> generate SIGTERM from the terminal; so I can see where if someone hasn't
>> read the postgres man page carefully, their first instinct upon finding
>> that control-C doesn't get them out of single-user mode might be to type
>> control-\ (or whatever the local QUIT character is). It doesn't seem
>> like it should be quite that easy to force a panic stop.
> That seems reasonable, but I know an awful lot of people that don't know
> how to generate SIGQUIT at all (I only learned about it about a year
> ago, I think). In fact anyone who doesn't already know that Ctrl-D
> closes the session is not very likely to know about Ctrl-\.
Sure, but those who do know how to SIGQUIT might reach for that before
they reach for control-D. There's hardly anyone out there who could
be called an experienced user of the standalone mode, I think, and so
we shouldn't assume that users always know control-D is the way out.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Tolley | 2007-07-08 23:56:41 | Re: The speed problem of Varchar vs. Char |
Previous Message | Martin Gainty | 2007-07-08 23:52:33 | Re: The speed problem of Varchar vs. Char |
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2007-07-09 00:38:35 | Re: [GENERAL] Unable to get postgres running after long time no vacuum |
Previous Message | Alvaro Herrera | 2007-07-08 22:49:14 | Re: [GENERAL] Unable to get postgres running after long time no vacuum |