Re: libpq stricter integer parsing

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: libpq stricter integer parsing
Date: 2018-09-07 13:45:10
Message-ID: 1241c86a-e243-8d2e-88eb-d056adfc2cad@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 17/08/2018 12:13, Fabien COELHO wrote:
> sh> psql "connect_timeout=2,port=5433"
>
> The timeout is set to 2, and the port directive is silently ignored.
> However, URL parsing is stricter, eg on "port".
>
> The attached patch checks integer syntax errors and overflows, and report
> errors.

This looks useful and the patch looks reasonable, but it doesn't apply
anymore. Can you send in an update?

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2018-09-07 13:57:01 Re: Removing useless \. at the end of copy in pgbench
Previous Message Peter Eisentraut 2018-09-07 13:28:10 Re: libpq debug log