On Mon, 2013-05-13 at 15:22 -0700, Peter Geoghegan wrote:
> On Tue, May 7, 2013 at 7:01 PM, Tom Lane wrote:
> > It seems reasonable to me to reduce it to DEBUG1 level.
>
> Attached patch renders all "loaded library..." messages DEBUG1,
> regardless of whether local_preload_libraries or
> shared_p
On Tue, Jun 4, 2013 at 5:46 AM, Andres Freund wrote:
> I don't really see a point in delaying it towards 9.4.
Me neither, obviously. It's not as if someone was willing to speak in
defense of the current behavior.
--
Peter Geoghegan
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postg
On 2013-06-04 08:39:18 -0400, Peter Eisentraut wrote:
> On 6/3/13 8:19 PM, Peter Geoghegan wrote:
> > On Mon, May 13, 2013 at 3:22 PM, Peter Geoghegan wrote:
> >> Attached patch renders all "loaded library..." messages DEBUG1,
> >> regardless of whether local_preload_libraries or
> >> shared_prelo
On 6/3/13 8:19 PM, Peter Geoghegan wrote:
> On Mon, May 13, 2013 at 3:22 PM, Peter Geoghegan wrote:
>> Attached patch renders all "loaded library..." messages DEBUG1,
>> regardless of whether local_preload_libraries or
>> shared_preload_libraries is involved, and regardless of EXEC_BACKEND.
>
> C
On Mon, May 13, 2013 at 3:22 PM, Peter Geoghegan wrote:
> Attached patch renders all "loaded library..." messages DEBUG1,
> regardless of whether local_preload_libraries or
> shared_preload_libraries is involved, and regardless of EXEC_BACKEND.
Can someone take a look at this, please? I'd rather
On Tue, May 7, 2013 at 7:01 PM, Tom Lane wrote:
> It seems reasonable to me to reduce it to DEBUG1 level.
Attached patch renders all "loaded library..." messages DEBUG1,
regardless of whether local_preload_libraries or
shared_preload_libraries is involved, and regardless of EXEC_BACKEND.
--
Pet
On Tue, May 7, 2013 at 7:01 PM, Tom Lane wrote:
> On the other hand, if we have it as DEBUG2 in the EXEC_BACKEND code
> path, I would be willing to argue that that's too low. If you're
> starting to feel a need to inquire into the backend's behavior, knowing
> about loaded modules seems like one
Peter Eisentraut writes:
> On Tue, 2013-05-07 at 14:28 -0700, Peter Geoghegan wrote:
>> It seems like an oversight to me that local_preload_libraries causes a
>> new log message to appear each time a new connection is established.
> It is correct in my view (but perhaps I have just gotten used to
On Tue, 2013-05-07 at 14:28 -0700, Peter Geoghegan wrote:
> It seems like an oversight to me that local_preload_libraries causes a
> new log message to appear each time a new connection is established.
It is correct in my view (but perhaps I have just gotten used to it),
but I wouldn't mind if you
It seems like an oversight to me that local_preload_libraries causes a
new log message to appear each time a new connection is established.
Is there any sympathy for the view that we should have a way of
turning this off, or simply not log such messages? We could still have
it appear at DEBUG2 lev
10 matches
Mail list logo
