| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: less log level for success dynamic background workers for 9.5 |
| Date: | 2015-06-24 23:39:12 |
| Message-ID: | 558B3FA0.8010000@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 6/23/15 8:11 PM, Craig Ringer wrote:
> I've certainly had similar issues to you w.r.t. to debug messages from
> user-level code, and wanted to be able to enable one particular log
> line, all log output from a particular function, or all log output
> from a particular extension / all functions in a schema.
I would also like the ability to potentially change the log level for
all calls made out of a certain function/schema/etc. Basically, change
it for everything below a certain entry in the call stack.
> I think it's a whole separate topicto Pavel's original proposal
> though, and really merits a separate thread. For Pavel's issue I'm all
> in favour of just changing the log message, I think LOG is way too
> high for something that's internal implementation detail.
+1.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2015-06-24 23:41:01 | Re: pg_stat_*_columns? |
| Previous Message | Tom Lane | 2015-06-24 23:19:22 | Re: Should we back-patch SSL renegotiation fixes? |