BUG #9251: default values for fatal error logging in service

From: krichter722(at)aol(dot)de
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #9251: default values for fatal error logging in service
Date: 2014-02-17 04:00:35
Message-ID: 20140217040035.24616.96063@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 9251
Logged by: Karl Richter
Email address: krichter722(at)aol(dot)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 :)

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2014-02-17 04:19:35 Re: BUG #9251: default values for fatal error logging in service
Previous Message Bruce Momjian 2014-02-15 16:52:44 Re: BUG #8540: Avoid sscanf buffer overflow