elog(LOG), elog(DEBUG) - Mailing list pgsql-hackers

From Peter Eisentraut
Subject elog(LOG), elog(DEBUG)
Date
Msg-id Pine.LNX.4.30.0105051048001.769-100000@peter.localdomain
Whole thread Raw
Responses Re: elog(LOG), elog(DEBUG)  (Alfred Perlstein <bright@wintelcom.net>)
Re: elog(LOG), elog(DEBUG)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
There's a TODO item to make elog(LOG) a separate level.  I propose the
name INFO.  It would be identical to DEBUG in effect, only with a
different label.  Additionally, all DEBUG logging should either be
disabled unless the debug_level is greater than zero, or alternatively
some elog(DEBUG) calls should be converted to INFO conditional on a
configuration setting (like log_pid, for example).

The stricter distinction between DEBUG and INFO would also yield the
possibility of optionally sending DEBUG output to the frontend, as has
been requested a few times.

-- 
Peter Eisentraut   peter_e@gmx.net   http://funkturm.homeip.net/~peter



pgsql-hackers by date:

Previous
From: David McWherter
Date:
Subject: GiST indexing problems...
Next
From: Alfred Perlstein
Date:
Subject: Re: elog(LOG), elog(DEBUG)