Re: [HACKERS] log_autovacuum_min_duration doesn't log VACUUMs
От | Jim Nasby |
---|---|
Тема | Re: [HACKERS] log_autovacuum_min_duration doesn't log VACUUMs |
Дата | |
Msg-id | 2d03d176-a4a6-8d58-d9ab-9fc0923100ff@BlueTreble.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] log_autovacuum_min_duration doesn't log VACUUMs (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: [HACKERS] log_autovacuum_min_duration doesn't log VACUUMs
|
Список | pgsql-hackers |
On 2/10/17 2:33 PM, Robert Haas wrote: > That having been said, I think it could certainly be useful to have > more control over what DDL gets logged in foreground processes. 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. -- 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 по дате отправления: