From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Scot Loach" <sloach(at)sandvine(dot)com> |
Cc: | <pgsql-odbc(at)postgresql(dot)org> |
Subject: | Re: [PATCH] notice handler |
Date: | 2005-09-17 22:30:16 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E4CC2CF9@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 Tom Lane
> Sent: 17 September 2005 23:20
> To: Scot Loach
> Cc: pgsql-odbc(at)postgresql(dot)org
> Subject: Re: [ODBC] [PATCH] notice handler
>
> "Scot Loach" <sloach(at)sandvine(dot)com> writes:
> > This patch fill fix the notice handler so that the odbc
> driver doesn't output notices from the backend to stderr.
>
> Why is that a "fix" and not "breaking it"? It sounds pretty
> ill-advised
> to me. In particular, notices sent when not inside a query
> are usually
> pretty significant (ie, the backend telling you why it's about to cut
> off your connection), and I can't see a justification for arbitrarily
> suppressing them.
It doesn't suppress them, it processes them as a non-fatal message so
the app can deal with them rather than just dumping them to stderr.
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-09-17 22:33:42 | Re: [PATCH] notice handler |
Previous Message | Dave Page | 2005-09-17 22:27:44 | Re: [PATCH] notice handler |