Re: Syslog and pg_options (for RPMs)

> However, it's folly to imagine that we will ever get rid of stderr
> output entirely.  One glaring example is that on most platforms,
> if you have a failure while trying to load a dynamic-link library,
> the dynamic linker will emit useful messages (like the names of
> unresolved symbols) on stderr.  It will never be acceptable to throw
> that info away, nor do we have a way to capture it and send it
> elsewhere than stderr.
> 
> Given these considerations, I'm not all that excited about mounting a
> holy war on stdout/stderr messages in the backend code.  It'd be more
> profitable to leave the code as-is and figure out a way to cause
> stdout/stderr output to be logged in a more admin-friendly manner.
> I like the idea of piping the output to a log-rotation program.

I am not out to eliminate it.  I just want to be sure that we are using
elog()/fprintf() in the proper places.  If someone says we are, the item
is closed.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026