BUG #9251: default values for fatal error logging in service - Mailing list pgsql-bugs

From krichter722@aol.de
Subject BUG #9251: default values for fatal error logging in service
Date
Msg-id 20140217040035.24616.96063@wrigleys.postgresql.org
Whole thread Raw
Responses Re: BUG #9251: default values for fatal error logging in service  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
The following bug has been logged on the website:

Bug reference:      9251
Logged by:          Karl Richter
Email address:      krichter722@aol.de
PostgreSQL version: 9.3.1
Operating system:   Ubuntu 13.10 on Linux 3.11
Description:

The logging of fatal errors when running postgresql as a service on debian
based systems, like Ubuntu, has a wrong default value. Without going into
details of the underlying error, I'll just give the following example:
invoking <code>sudo service postgresql start</code> gives the output
<output>Error: Invalid data directory</code>. The default value for such
fatal errors should be set to a higher verbosity so that detailed
information and instructions about the error in the data directory (I assume
that pgsql has such function) are logged to stdout (which should also become
the default setting for logging output when starting pgsql as service).
There's no advantage in letting the user search for log output in numerous
of files and going through pages and pages of logging docs. The potential
use for contradictory use case which is to provide no information at all
after a fatal error is fairly small :)

pgsql-bugs by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: BUG #8540: Avoid sscanf buffer overflow
Next
From: Tom Lane
Date:
Subject: Re: BUG #9251: default values for fatal error logging in service