
Just lookign through elog.c to see how I can improve logging, so taht I
can get more information from the backend.  We have the above mentioned
USE_SYSLOG in a few places:

pgsql% find . -name "*.[ch]" -exec grep USE_SYSLOG {} \; -print
#ifdef USE_SYSLOG
#ifdef USE_SYSLOG
#ifdef USE_SYSLOG
#ifdef USE_SYSLOG
./backend/utils/error/elog.c
#ifdef USE_SYSLOG
#ifdef USE_SYSLOG
#ifdef USE_SYSLOG
#ifdef USE_SYSLOG
#ifdef USE_SYSLOG
#ifdef USE_SYSLOG
#ifdef USE_SYSLOG
./backend/utils/misc/trace.c

But nowhere to actually define it (not even listed in config.h.in) ...

pg_options shows a 'syslog=2' capability, but, without SysLOG enabled, its
sort of useless ...

what I want to get is a PID/Timestamp in the log files ... suggestions?

Marc G. Fournier                   ICQ#7615664               IRC Nick: Scrappy
Systems Administrator @ hub.org 
primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org 


Mon, 8 May 2000 10:09:14 -0300 (ADT)
The Hermit Hacker <scrappy@hub.org>
USE_SYSLOG ... useless? :)
The Hermit Hacker wrote:
 
> But nowhere to actually define it (not even listed in config.h.in) ...
 
> pg_options shows a 'syslog=2' capability, but, without SysLOG enabled, its
> sort of useless ...
 
> what I want to get is a PID/Timestamp in the log files ... suggestions?

Define USE_SYSLOG and ELOG_TIMESTAMPS in config.h.in (or config.h,
depending upon your preference to patching prior to or after running
configure). This is the default compile for the RPM's, incidentally.

I'm surprized no one else answered -- I figured you'd have your answer
by now.

--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11

Mon, 08 May 2000 20:23:08 -0400
Lamar Owen <lamar.owen@wgcr.org>
Re: USE_SYSLOG ... useless? :)