Re: maximum for auto_explain.log_min_duration doesn't seem to makesense - Mailing list pgsql-bugs

From David Gould
Subject Re: maximum for auto_explain.log_min_duration doesn't seem to makesense
Date
Msg-id 20180223133627.33672e01@engels
Whole thread Raw
In response to Re: maximum for auto_explain.log_min_duration doesn't seem to make sense  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Fri, 23 Feb 2018 14:25:59 -0500
Tom Lane <tgl@sss.pgh.pa.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@sonic.net
If simplicity worked, the world would be overrun with insects.


pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #15084: Invalid LIKE pattern not always reported
Next
From: Peter Eisentraut
Date:
Subject: Re: BUG #15044: materialized views incompatibility with logicalreplication in postgres 10