postgres.git / summary / log / commit / refs

commit    be87cd2a0aa02428084c83b59d10a2c033e0ae81
Author:   Tom Lane <tgl@sss.pgh.pa.us>
Date:     Fri Feb 23 19:38:19 2018 +0000
First released in: 11.0, 9.3.22, 9.4.17, 9.5.12, 9.6.8, 10.3

    Allow auto_explain.log_min_duration to go up to INT_MAX.
    
    The previous limit of INT_MAX / 1000 seems to have been cargo-culted in
    from somewhere else.  Or possibly the value was converted to microseconds
    at some point; but in all supported releases, it's just compared to other
    values, so there's no need for the restriction.  This change raises the
    effective limit from ~35 minutes to ~24 days, which conceivably is useful
    to somebody, and anyway it's more consistent with the range of the core
    log_min_duration_statement GUC.
    
    Per complaint from Kevin Bloch.  Back-patch to all supported releases.
    
    Discussion: https://postgr.es/m/8ea82d7e-cb78-8e05-0629-73aa14d2a0ca@codingthat.com


 contrib/auto_explain/auto_explain.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/contrib/auto_explain/auto_explain.c b/contrib/auto_explain/auto_explain.c
index 4ccd2aa8490..29937ba1d89 100644
--- a/contrib/auto_explain/auto_explain.c
+++ b/contrib/auto_explain/auto_explain.c
@@ -78,7 +78,7 @@ _PG_init(void)
 						 "Zero prints all plans. -1 turns this feature off.",
 							&auto_explain_log_min_duration,
 							-1,
-							-1, INT_MAX / 1000,
+							-1, INT_MAX,
 							PGC_SUSET,
 							GUC_UNIT_MS,
 							NULL,


[parent: b67383789e90]