mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Parse libpq's "keepalives" option more like other integer options.

Browse Source 
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
This commit is contained in:
Tom Lane 2024-10-02 17:30:36 -04:00 committed by Muhammad Usama
parent 5465846054
commit 4281ba3f0c
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
src/interfaces/libpq/fe-connect.c
View File

@ -2168,14 +2168,14 @@ connectFailureMessage(PGconn *conn, int errorno)
static int
useKeepalives(PGconn *conn)
{
char *ep;
int val;
if (conn->keepalives == NULL)
return 1;
val = strtol(conn->keepalives, &ep, 10);
if (*ep)
if (!pqParseIntParam(conn->keepalives, &val, conn, "keepalives"))
return -1;
return val != 0 ? 1 : 0;
}
@ -3083,7 +3083,7 @@ keep_going: /* We will come back to here until there is
if (usekeepalives < 0)
{
libpq_append_conn_error(conn, "keepalives parameter must be an integer");
/* error is already reported */
err = 1;
}
else if (usekeepalives == 0)