Received: from secure.arcamax.com (secure.arcamax.com [209.96.210.67])
	by hub.org (8.10.1/8.10.1) with ESMTP id e8FEnes88364
	for <pgsql-interfaces@postgreSQL.org>;
	Fri, 15 Sep 2000 10:49:40 -0400 (EDT)
Received: from bryan2 (bryan [209.96.210.45])
	by secure.arcamax.com (8.9.3/8.9.3) with SMTP id KAA10799
	for <pgsql-interfaces@postgreSQL.org>; Fri, 15 Sep 2000 10:49:47 -0400
Message-ID: <004301c01f24$31534b80$2dd260d1@arcamax.com>
From: "Bryan White" <bryan@arcamax.com>
To: <pgsql-interfaces@postgreSQL.org>
Subject: Perl Interface is printing NOTICE's on stderr
Date: Fri, 15 Sep 2000 10:49:47 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
X-Archive-Number: 200009/58

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.  I routinely call this funct when making a database
connection and it in combination with pids in the log file it is much easier
to correlate client programs with error messages.

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?

Bryan White