[CLUE-Tech] PostgreSQL (non-)error logging on RedHat

[Ed Hill]

On Fri, 2003-12-19 at 15:34, Matt Gushee wrote:
> Well, yesterday I put up an online demo of my magnificent new software
> package, which uses PostgreSQL. And sometime last night or early this
> morning, PostgreSQL crashed. So of course, I went looking for the log
> file to see if I could find out why. Much to my chagrin, I found there
> was no log file--and now I know why: RedHat Linux 8.0 starts PostgreSQL
> like this (c&p'ed from /etc/init.d/postgresql):
> 
>     su -l postgres -s /bin/sh -c "/usr/bin/pg_ctl  -D $PGDATA -p \
>         /usr/bin/postmaster start  > /dev/null 2>&1" < /dev/null
> 
> ... so all the output is going to /dev/null ?!! Both common sense and
> the PostgreSQL manual strongly recommend keeping a log ... but before I
> go ahead and fix it, is there any good reason for *not* logging? Or
> should RedHat be drawn and quartered for this?


Hi Matt,

The no-postgres-log problem exists on RH 9, too.  Discovered that when
configuring GForge on a couple of systems.  Yeah, its a lousy default
but perhaps not enough to warrant the "drawn and quartered" option.  If
you submit an RFE on bugzilla.redhat.com and send me the bug ID, I'll
promise to add a "me too" comment to it.  ;-)

Ed

-- 
Edward H. Hill III, PhD
office:  MIT Dept. of EAPS;  Room 54-1424;  77 Massachusetts Ave.
            Cambridge, MA 02139-4307
email:   eh3 at mit.edu,  ed at eh3.com
URL:     http://web.mit.edu/eh3/
phone:   617-253-0098
fax:     617-253-4464
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://cluedenver.org/pipermail/clue-tech/attachments/20031219/0fad83b7/attachment.bin