| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: log_autovacuum_min_duration doesn't log VACUUMs |
| Date: | 2017-02-13 02:20:34 |
| Message-ID: | 2d03d176-a4a6-8d58-d9ab-9fc0923100ff@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2017-02-13 02:29:25 | Re: gitlab post-mortem: pg_basebackup waiting for checkpoint |
| Previous Message | Jim Nasby | 2017-02-13 02:09:34 | Re: removing tsearch2 |