Received: from sss.pgh.pa.us (tlane-gw0.cust.stargate.net [209.114.132.154])
	by hub.org (8.10.1/8.10.1) with ESMTP id e8FJABs27004
	for <pgsql-interfaces@postgresql.org>;
	Fri, 15 Sep 2000 15:10:11 -0400 (EDT)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.11.0/8.11.0) with ESMTP id e8FJA9B00115;
	Fri, 15 Sep 2000 15:10:09 -0400 (EDT)
To: "Bryan White" <bryan@arcamax.com>
cc: pgsql-interfaces@postgresql.org
Subject: Re: Perl Interface is printing NOTICE's on stderr 
In-reply-to: <004301c01f24$31534b80$2dd260d1@arcamax.com> 
References: <004301c01f24$31534b80$2dd260d1@arcamax.com>
Comments: In-reply-to "Bryan White" <bryan@arcamax.com>
	message dated "Fri, 15 Sep 2000 10:49:47 -0400"
Date: Fri, 15 Sep 2000 15:10:09 -0400
Message-ID: <112.969045009@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Archive-Number: 200009/59

"Bryan White" <bryan@arcamax.com> writes:
> I have a function that I have added to the database that prints a client
> sighon message to the backends log file.  It uses elog(NOTICE...) to write
> to the log file.
> My problem is that when the client side is a perl program using the Pg
> module, the NOTICE messages are also printed on the client side.  I think
> they are going to stderr.

> Can someone suggest how to prevent this?

Try elog(DEBUG, ...) instead.

			regards, tom lane