apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bob Rossi <bob_ro...@cox.net>
Subject Re: dbd postgresql
Date Fri, 30 May 2008 12:48:11 GMT
On Fri, May 30, 2008 at 12:00:11PM +0100, Nick Kew wrote:
> On Fri, 30 May 2008 17:47:23 +1000
> Bojan Smojver <bojan@rexursive.com> wrote:
> 
> > On Fri, 2008-05-30 at 01:50 -0500, William A. Rowe, Jr. wrote:
> > 
> > > So if it's possible with the postgresql to mute the stdout
> > > information, we really need to do so.
> > 
> > I'm not convinced of the usefulness of this, but here is the patch
> > nevertheless.
> > 
> Wouldn't a better patch be to save the message internally so that
> a subsequent dbd_pgsql_error picks it up?
> 
> Not exactly critical - just a thought.

Maybe a way to allow the user to get access to the messages too?

I did notice that when I do this on startup, 
  set client_min_messages = 'WARNING';
that the messages stop. Perhaps this is a good enough work around?

I'm not sure, I don't know entirely the philosophy of the apr group.

Bob Rossi

Mime
View raw message