Re: notice handler in libpq-based driver - Mailing list pgsql-odbc

From Dave Page
Subject Re: notice handler in libpq-based driver
Date
Msg-id E7F85A1B5FF8D44C8A1AF6885BC9A0E4AC9F04@ratbert.vale-housing.co.uk
Whole thread Raw
In response to notice handler in libpq-based driver  ("Scot Loach" <sloach@sandvine.com>)
Responses Re: notice handler in libpq-based driver  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-odbc

> -----Original Message-----
> From: pgsql-odbc-owner@postgresql.org
> [mailto:pgsql-odbc-owner@postgresql.org] On Behalf Of Scot Loach
> Sent: 06 September 2005 19:18
> To: pgsql-odbc@postgresql.org
> Subject: [ODBC] notice handler in libpq-based driver
>
> With the new driver I sometimes see messages being printed to
> stderr, obviously the ODBC driver should not do this.
> I believe the PQnoticeProcessor needs to be set, see this
> documentation for details of how this works.
> http://www.postgresql.org/docs/7.4/interactive/libpq-notice-pr
> ocessing.html
>
> It should be trivial to add this but I'm not sure what the
> best place to do it would be, would one of the maintainers be
> able to do it?

No, I'm not sure how to handle this either - the old driver handled it
in the socket code along with other messages. I'm not sure how, with the
noticeProcessor, we would associate notices with specific statements or
connections.

I suppose we could just store them all someplace, and check/empty the
list after each libpq_execute.

Anoop, what do you think?

Regards, Dave.

pgsql-odbc by date:

Previous
From: "Dave Page"
Date:
Subject: Re: Critical Bug with UseDeclareFetch in development version
Next
From: Carlos Henrique Reimer
Date:
Subject: Application bottlenecks