Re: Syslog and pg_options (for RPMs)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
Cc: 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 02:25:45
Message-ID: 15434.981685545@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Justin Clift 2001-02-09 02:33:30 SPI_exec - Trying to access SPI_tuptable - error of 'dereferencing pointer to incomplete type'
Previous Message Tatsuo Ishii 2001-02-09 02:12:57 Re: Syslog and pg_options (for RPMs)