| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: local_preload_libraries logspam |
| Date: | 2013-05-08 03:25:32 |
| Message-ID: | CAM3SWZSCcfxPETw-YftTd9tmwceSrZPMaD0ngvSgmKsXfgxnKw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, May 7, 2013 at 7:01 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2013-05-08 03:38:44 | Re: XLogFlush invoked about twice as many times after 9.2 group commit enhancement |
| Previous Message | Alvaro Herrera | 2013-05-08 03:18:33 | Re: Make targets of doc links used by phpPgAdmin static |