From: | David Gould <daveg(at)sonic(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Kevin Bloch <kev(at)codingthat(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: maximum for auto_explain.log_min_duration doesn't seem to make sense |
Date: | 2018-02-23 21:36:27 |
Message-ID: | 20180223133627.33672e01@engels |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Fri, 23 Feb 2018 14:25:59 -0500
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> INT_MAX. As to whether it's worth doing, the existing limit is equivalent
> to ~35 minutes if I did the math right. I can barely imagine that anyone
> would want to set auto_explain.log_min_duration higher than that, but
> maybe in some huge data warehouse environment it'd make sense.
> In short, seems like a valid complaint to me.
A client has several production queries that commonly run an hour or two.
Sometimes queries are modified infelicitously or the planner is lead astray
due to statistics etc and they can run much longer unexpectedly. It would be
useful to set a threshold of a few hours to catch those as reproducing them
is a slow process.
-dg
--
David Gould daveg(at)sonic(dot)net
If simplicity worked, the world would be overrun with insects.
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2018-02-23 22:31:20 | Re: BUG #15044: materialized views incompatibility with logical replication in postgres 10 |
Previous Message | Tom Lane | 2018-02-23 20:51:41 | Re: BUG #15084: Invalid LIKE pattern not always reported |