diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2018-02-23 14:38:19 -0500 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2018-02-23 14:39:21 -0500 |
| commit | 753875ed42fd3f854933684c5f8f7358b1a16172 (patch) | |
| tree | 5a70d15331a25111b158213128732af31e31cdaa /src/backend/utils/adt/arrayfuncs.c | |
| parent | 269dce481c36d0ac0b9bb14b48f9f4d59ac5faf1 (diff) | |
| download | postgresql-753875ed42fd3f854933684c5f8f7358b1a16172.tar.gz postgresql-753875ed42fd3f854933684c5f8f7358b1a16172.zip | |
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
Diffstat (limited to 'src/backend/utils/adt/arrayfuncs.c')
0 files changed, 0 insertions, 0 deletions