Re: Syslog and pg_options (for RPMs)

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>, <lamar(dot)owen(at)wgcr(dot)org>, <pgman(at)candle(dot)pha(dot)pa(dot)us>, <dz(at)cs(dot)unitn(dot)it>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Syslog and pg_options (for RPMs)
Date: 2001-02-09 17:35:20
Message-ID: Pine.LNX.4.30.0102091833490.1286-100000@peter.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane writes:

> Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> 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 peter_e(at)gmx(dot)net http://yi.org/peter-e/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-02-09 17:44:16 Re: [HACKERS] Open 7.1 items
Previous Message Bruce Momjian 2001-02-09 17:26:19 Open 7.1 items