Re: local_preload_libraries logspam - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: local_preload_libraries logspam
Date
Msg-id CAM3SWZSCcfxPETw-YftTd9tmwceSrZPMaD0ngvSgmKsXfgxnKw@mail.gmail.com
Whole thread Raw
In response to Re: local_preload_libraries logspam  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, May 7, 2013 at 7:01 PM, Tom Lane <tgl@sss.pgh.pa.us> 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 of the first things you need to know
> about.  Hence, I'd vote for DEBUG1.

+1 to DEBUG1.


-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Make targets of doc links used by phpPgAdmin static
Next
From: Peter Geoghegan
Date:
Subject: Re: XLogFlush invoked about twice as many times after 9.2 group commit enhancement