From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2)
Description of problem:
Postgres has features to log debug output, queries etc. to
stdout/stderr. The rhdb start script redirects this to /dev/null.
It should be possible to configure this to log into a file,
or even better into a program, so that this output is lost.
Currently this cannot be done safely, because /etc/rc.d/init.d/rhdb
is not marked to be a configuration file, so changes would be lost
on an update.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. look into the rhdb service start file where postmaster is started
2. notice the >/dev/null 2&>1
Actual Results: output logged to the bit bucket
Expected Results: A possibility, either by setting a variable in
to log to a file or a program, alternatively setting the start script
to be a config file so that changes can be made safely.
Inhouse, we pipe the log to /usr/sbin/rotatelogs from the httpd package
and use tmpwatch to clean out older logfiles. This would however be
a bad default configuration because it adds dependencies to httpd.
A sysconfig configuration variable, which can default to
>/dev/null would have zero impact on current system, but make
advanced logging possible.
Internal RFE bug #114775 added. Will be considered for future releases.
Postgres server not supported in RHEL3.