From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
---|---|
To: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> |
Cc: | "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, "ik(at)postgresql-consulting(dot)com" <ik(at)postgresql-consulting(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Wait events monitoring future development |
Date: | 2016-08-10 06:34:29 |
Message-ID: | CAMsr+YEZkNTAe9K_5rd8EVkTHUjnvUcxqsz=LSp_ncv-fabE9A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 10 August 2016 at 07:09, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> wrote:
>
>
The downside to leaving stuff like this off by default is users won't
> remember it's there when they need it. At best, that means they spend more
> time debugging something than they need to. At worse, it means they suffer
> a production outage for longer than they need to, and that can easily
> exceed many months/years worth of the extra cost from the monitoring
> overhead.
>
Yeah.. and I've got to say, the whole "it'll hurt benchmarks if it's on by
default" argument falls flat on its face when you look at our defaults for
shared_buffers, etc.
If you don't tune Pg, it runs reliably, but slowly. If this proves to have
"reasonable" overhead, I'd be inclined to say it should just be on. I
frequently wish auto_explain and pg_stat_statements were in-core and
on-by-default so when someone calls saying things got slow the historical
data is already there. I'm sure this'll be the same.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2016-08-10 06:44:49 | Re: PATCH: Batch/pipelining support for libpq |
Previous Message | Dilip Kumar | 2016-08-10 05:57:50 | Re: [sqlsmith] Failed assertion in joinrels.c |