aboutsummaryrefslogtreecommitdiff
path: root/src/bin/scripts/dropuser.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2018-02-23 14:38:19 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2018-02-23 14:39:22 -0500
commit3ba503bde9aede23db6d35c00706daab15015f35 (patch)
tree6dc56a771ed348b9140fcfa145bdfc7bdff2c221 /src/bin/scripts/dropuser.c
parentda27155c6b79e84f29bd71eab662b23f3da970e8 (diff)
downloadpostgresql-3ba503bde9aede23db6d35c00706daab15015f35.tar.gz
postgresql-3ba503bde9aede23db6d35c00706daab15015f35.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/bin/scripts/dropuser.c')
0 files changed, 0 insertions, 0 deletions