The 'client' side. Thanks, I'll give it a try.
Tim
- Original Message -
From: "Tom Lane" <[EMAIL PROTECTED]>
To: "Tim Barnard" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, June 04, 2001 1:40 PM
Subject: Re: [GENERAL] li
"Tim Barnard" <[EMAIL PROTECTED]> writes:
> Is there any way to force Postgre not to send NOTICEs to the console?
Define "console" --- you mean the client's stderr? Or the postmaster's?
Changing libpq's notice processor (see PQsetNoticeProcessor) would help
if you want to filter notices on the
ther ideas? This is really driving me bonkers!?!?! :-)
Tim
- Original Message -
From: "Andrew Sullivan" <[EMAIL PROTECTED]>
To: "Tim Barnard" <[EMAIL PROTECTED]>
Sent: Monday, June 04, 2001 11:23 AM
Subject: Re: [GENERAL] libpq and PostgreSQL NOTICEs
&
Is there any way to force Postgre not to send
NOTICEs to the console? I have an ncurses app that from time to time gets
notices stating that "begin is already a transaction in progress." Now I know I
need to track down where I'm issuing a "begin" twice, but I would rather Postgre
log these w
