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 whethe

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

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

2001-05-05 Thread Alfred Perlstein
* Peter Eisentraut <[EMAIL PROTECTED]> [010505 02:06] wrote: > 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