Re: [GENERAL] Unable to get postgres running after long time no vacuum - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [GENERAL] Unable to get postgres running after long time no vacuum
Date
Msg-id 21354.1183942780@sss.pgh.pa.us
Whole thread Raw
In response to Re: [GENERAL] Unable to get postgres running after long time no vacuum  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: [GENERAL] Unable to get postgres running after long time no vacuum  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
Alvaro Herrera <alvherre@commandprompt.com> writes:
> Tom Lane wrote:
>> 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.

> I agree completely, but is that an argument _against_ a "quit" command?

No, it's orthogonal to whether we want a "quit" command.  (My opinion is
not, because what the heck will we do with it in multiuser mode?  And
there is no good way to shoehorn it into just the single-user mode, it'd
have to be a grammar entry.)
        regards, tom lane


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: [GENERAL] Unable to get postgres running after long time no vacuum
Next
From: Alvaro Herrera
Date:
Subject: Re: [GENERAL] Unable to get postgres running after long time no vacuum