Re: Syslog and pg_options (for RPMs)
От | Lamar Owen |
---|---|
Тема | Re: Syslog and pg_options (for RPMs) |
Дата | |
Msg-id | 3A82F0C6.CC884790@wgcr.org обсуждение исходный текст |
Ответ на | Re: Syslog and pg_options (for RPMs) (Bruce Momjian <pgman@candle.pha.pa.us>) |
Ответы |
Re: Syslog and pg_options (for RPMs)
|
Список | pgsql-hackers |
Bruce Momjian wrote: > > 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. Where is elog() safe? (Going to Bruce 'comb through the archives' mode here...) If someone can educate me in that, I can tackle doing this. Don't know if I can do so before 7.1 release, but I'll certainly try. -- Lamar Owen WGCR Internet Radio 1 Peter 4:11
В списке pgsql-hackers по дате отправления: