> AFAIR, elog at NOTICE or DEBUG level isn't really supposed to have any
> side-effects. The bigger issue is that you have to be careful about
> using it in certain places, mainly during startup or for reporting
> communication errors. (send failure -> elog -> tries to send message to
> client -> send failure -> elog -> trouble)
>
> Also, I believe most of the printf's in the backend are in debugging
> support code that's not even compiled by default. The return on
> investment from converting those routines to use elog is really nil.
> There may be a few remaining printf calls that should be converted to
> elog, but I don't think this is a big issue.
Clearly not a big issue, but something someone can poke around at to get
started.
--
Bruce Momjian | http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster
