From: | "Tim Barnard" <tbarnard(at)povn(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: libpq and PostgreSQL NOTICEs |
Date: | 2001-06-04 20:44:49 |
Message-ID: | 017f01c0ed37$33789aa0$a519af3f@hartcomm.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
The 'client' side. Thanks, I'll give it a try.
Tim
----- Original Message -----
From: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Tim Barnard" <tbarnard(at)povn(dot)com>
Cc: <pgsql-general(at)postgresql(dot)org>
Sent: Monday, June 04, 2001 1:40 PM
Subject: Re: [GENERAL] libpq and PostgreSQL NOTICEs
> "Tim Barnard" <tbarnard(at)povn(dot)com> 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 client side.
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | HYip | 2001-06-04 20:46:09 | getting non-atomic field with C API |
Previous Message | Tom Lane | 2001-06-04 20:40:24 | Re: libpq and PostgreSQL NOTICEs |