Re: debugger.c tries to set log_min_messages, why? - Mailing list pgadmin-hackers

From Guillaume Lelarge
Subject Re: debugger.c tries to set log_min_messages, why?
Date
Msg-id 1392050656.2537.77.camel@localhost
Whole thread Raw
In response to Re: debugger.c tries to set log_min_messages, why?  (Ashesh Vashi <ashesh.vashi@enterprisedb.com>)
Responses Re: debugger.c tries to set log_min_messages, why?
List pgadmin-hackers
On Mon, 2014-02-10 at 21:59 +0530, Ashesh Vashi wrote:
> On Mon, Feb 10, 2014 at 9:54 PM, Guillaume Lelarge
> <guillaume@lelarge.info>wrote:
>
> > On Mon, 2014-02-10 at 21:46 +0530, Ashesh Vashi wrote:
> > > On Sat, Feb 8, 2014 at 10:49 PM, Guillaume Lelarge
> > > <guillaume@lelarge.info>wrote:
> > >
> > > > Hi,
> > > >
> > > > Just a quick question. If you try to use the debugger, it executes a
> > > > "SET log_min_messages TO fatal", which denies any regular user to debug
> > > > his own functions. And actually, I don't see any reason why it should
> > > > set log_min_messages. If there is, which is it?
> > > >
> > > When redesigning the debugger, I did not modify the existing connection
> > > settings without much thoughts.
> > > After reading this mail, I couldn't agree more with you. It shouldn't be
> > > there.
> > >
> >
> > Good to know. Are you working on this, or should I provide a patch?
> >
> I will do it.
> Thanks
>

OK, thanks, Ashesh :)


--
Guillaume
http://blog.guillaume.lelarge.info
http://www.dalibo.com



pgadmin-hackers by date:

Previous
From: Ashesh Vashi
Date:
Subject: Re: debugger.c tries to set log_min_messages, why?
Next
From: "J.F. Oster"
Date:
Subject: PATCH: Fix bug in inherited column definition