aboutsummaryrefslogtreecommitdiff
path: root/src/tutorial/complex.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2024-10-02 17:30:36 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2024-10-02 17:30:36 -0400
commitbb8c89dbcde713b56b644cb42519db884d59ed91 (patch)
treee8a7a0b9ad9a4767364a17e7c1ec0e35a744e84e /src/tutorial/complex.c
parent41ab4568043bfaf0756bf43f89862ce0fc0006ee (diff)
downloadpostgresql-bb8c89dbcde713b56b644cb42519db884d59ed91.tar.gz
postgresql-bb8c89dbcde713b56b644cb42519db884d59ed91.zip
Parse libpq's "keepalives" option more like other integer options.
Use pqParseIntParam (nee parse_int_param) instead of using strtol directly. This allows trailing whitespace, which the previous coding didn't, and makes the spelling of the error message consistent with other similar cases. This seems to be an oversight in commit e7a221797, which introduced parse_int_param. That fixed places that were using atoi(), but missed this place which was randomly using strtol() instead. Ordinarily I'd consider this minor cleanup not worth back-patching. However, it seems that ecpg assumes it can add trailing whitespace to URL parameters, so that use of the keepalives option fails in that context. Perhaps that's worth improving as a separate matter. In the meantime, back-patch this to all supported branches. Yuto Sasaki (some further cleanup by me) Discussion: https://postgr.es/m/TY2PR01MB36286A7B97B9A15793335D18C1772@TY2PR01MB3628.jpnprd01.prod.outlook.com
Diffstat (limited to 'src/tutorial/complex.c')
0 files changed, 0 insertions, 0 deletions