Re: Syslog and pg_options (for RPMs) - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Syslog and pg_options (for RPMs)
Date
Msg-id 200010091947.PAA16316@candle.pha.pa.us
Whole thread Raw
In response to Syslog and pg_options (for RPMs)  (Lamar Owen <lamar.owen@wgcr.org>)
List pgsql-hackers
Can someone address this?

> Bruce Momjian wrote:
> > 
> > Seems this was already done in 7.1, right?
> [thread on puts() and fprintf(stderr and printf instead of tprintf or
> replacement truncated]
> 
> There are still scads of fprintf(stderr, "some error message from
> postmaster or backend") lying around, in CURRENT as of this morning at
> 1:00AM EDT.  Some are things such as the usage message -- others are
> obviously (IMHO) things that need to be sent to the logs.  We're not
> replacing the system fprintf , are we? (my assumption is that we are
> NOT). The usage of puts(), OTOH, has been well nigh eradicated.
> 
> Try a find -name '*.[hc]' -print -exec grep printf \{\} \; with cwd=src
> to see.... (of course, that also exposes where we are continuing to use
> sprintf instead of snprintf, for whatever reason....)
> 
> Comments?
> 
> --
> Lamar Owen
> WGCR Internet Radio
> 1 Peter 4:11
> 


--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Proposal: TRUNCATE TABLE table RESTRICT
Next
From: Bruce Momjian
Date:
Subject: Re: Proposal for fixing numeric type-resolution issues