Tom Lane writes: > Tatsuo Ishii <[EMAIL PROTECTED]> writes: > > There are still many loggings using just plain fprintf(). They should > > be replaced by elog(DEBUG) or elog(NOTICE), IMHO. > > I don't disagree with doing that where it's convenient and safe (which > is not everywhere). I'm just pointing out that we need a solution that > covers stderr output as well. Couldn't we redirect stderr to do what we want? dup(), pipe(), fifo, who knows. -- Peter Eisentraut [EMAIL PROTECTED] http://yi.org/peter-e/
- Re: [HACKERS] Syslog and pg_options (for RPM... Nathan Myers
- Re: [HACKERS] Syslog and pg_options (for RPM... Tom Lane
- Re: [HACKERS] Syslog and pg_options (for RPM... Ian Lance Taylor
- Re: [HACKERS] Syslog and pg_options (for RPM... Vince Vielhaber
- Re: [HACKERS] Syslog and pg_options (for RPM... Nathan Myers
- Re: [HACKERS] Syslog and pg_options (for RPM... Oleg Bartunov
- Re: [HACKERS] Syslog and pg_options (for RPMs) Tom Lane
- Re: [HACKERS] Syslog and pg_options (for RPM... Lamar Owen
- Re: [HACKERS] Syslog and pg_options (for RPM... Tatsuo Ishii
- Re: [HACKERS] Syslog and pg_options (for RPM... Tom Lane
- Re: [HACKERS] Syslog and pg_options (for RPM... Peter Eisentraut
- Re: [HACKERS] Syslog and pg_options (for RPMs) Nathan Myers