From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Scot Loach" <sloach(at)sandvine(dot)com>, <pgsql-odbc(at)postgresql(dot)org> |
Cc: | "Anoop Kumar" <anoopk(at)pervasive-postgres(dot)com> |
Subject: | Re: notice handler in libpq-based driver |
Date: | 2005-09-07 08:38:06 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E4AC9F04@ratbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
> -----Original Message-----
> From: pgsql-odbc-owner(at)postgresql(dot)org
> [mailto:pgsql-odbc-owner(at)postgresql(dot)org] On Behalf Of Scot Loach
> Sent: 06 September 2005 19:18
> To: pgsql-odbc(at)postgresql(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Carlos Henrique Reimer | 2005-09-07 11:24:16 | Application bottlenecks |
Previous Message | Dave Page | 2005-09-07 08:10:03 | Re: Critical Bug with UseDeclareFetch in development version |