Re: [HACKERS] log_autovacuum_min_duration doesn't log VACUUMs
| От | Jim Nasby |
|---|---|
| Тема | Re: [HACKERS] log_autovacuum_min_duration doesn't log VACUUMs |
| Дата | |
| Msg-id | d1a712eb-9424-4d99-707d-eb729387523a@BlueTreble.com обсуждение |
| Ответ на | Re: [HACKERS] log_autovacuum_min_duration doesn't log VACUUMs (Robert Haas <robertmhaas@gmail.com>) |
| Список | pgsql-hackers |
On 2/13/17 11:12 AM, Robert Haas wrote: >> FWIW, this is a significant problem outside of DDL. Once you're past 1-2 >> levels of nesting SET client_min_messages = DEBUG becomes completely >> useless. >> >> I think the ability to filter logging based on context would be very >> valuable. AFAIK you could actually do that for manual logging with existing >> plpgsql support, but obviously that won't help for anything else.> > Well, that's moving the goalposts a lot further and in an unrelated > direction. Short of someone getting a flash of brilliance, I agree. I tried indicating as much with my "FWIW" but obviously that wasn't explicit enough. -- Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX Experts in Analytics, Data Architecture and PostgreSQL Data in Trouble? Get it in Treble! http://BlueTreble.com 855-TREBLE2 (855-873-2532)
В списке pgsql-hackers по дате отправления: