aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistvacuum.c
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2019-10-21 11:17:13 +0900
committerMichael Paquier <michael@paquier.xyz>2019-10-21 11:17:13 +0900
commit4f4061b2dde178d2ab79d1ee3b1ae3c62c117926 (patch)
treee95cfe2074fa70f632327e2818d13c64da90f980 /src/backend/access/gist/gistvacuum.c
parentea9e06ac66d3e9584950f52878c8e4b71f963610 (diff)
downloadpostgresql-4f4061b2dde178d2ab79d1ee3b1ae3c62c117926.tar.gz
postgresql-4f4061b2dde178d2ab79d1ee3b1ae3c62c117926.zip
Fix parsing of integer values for connection parameters in libpq
Commit e7a2217 has introduced stricter checks for integer values in connection parameters for libpq. However this failed to correctly check after trailing whitespaces, while leading whitespaces were discarded per the use of strtol(3). This fixes and refactors the parsing logic to handle both cases consistently. Note that trying to restrict the use of trailing whitespaces can easily break connection strings like in ECPG regression tests (these have allowed me to catch the parsing bug with connect_timeout). Author: Michael Paquier Reviewed-by: Lars Kanis Discussion: https://postgr.es/m/a9b4cbd7-4ecb-06b2-ebd7-1739bbff3217@greiz-reinsdorf.de Backpatch-through: 12
Diffstat (limited to 'src/backend/access/gist/gistvacuum.c')
0 files changed, 0 insertions, 0 deletions