[HACKERS] elog(LOG), elog(DEBUG)

2001-05-05 Thread Peter Eisentraut
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

Re: [HACKERS] elog(LOG), elog(DEBUG)

2001-05-05 Thread Tom Lane
Peter Eisentraut [EMAIL PROTECTED] writes: 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. This conveys nothing to my mind. How should I determine whether a given elog call ought to use

Re: [HACKERS] elog(LOG), elog(DEBUG)

2001-05-05 Thread Peter Eisentraut
Tom Lane writes: Peter Eisentraut [EMAIL PROTECTED] writes: 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. This conveys nothing to my mind. How should I determine whether a given