Re: [PATCH] psql: Make ParseVariableDouble reject values above max

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Sven Klemm <sven(at)tigerdata(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: [PATCH] psql: Make ParseVariableDouble reject values above max
Date: 2026-05-09 18:44:36
Message-ID: DF42FECA-1A0D-4CF7-AE64-8A438D2436E0@yesql.se
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 8 May 2026, at 17:39, Sven Klemm <sven(at)tigerdata(dot)com> wrote:
>
> Hello,
>
> ParseVariableDouble() in src/bin/psql/variables.c is asymmetric in how
> it handles the [min, max] bounds it documents. The lower-bound branch
> correctly returns false, but the upper-bound branch logs the error and
> then falls through to assign *result and return true. The function's
> contract ("the value must be within the range [min,max] in order to be
> considered valid"; "if unsuccessful, *result isn't clobbered") is
> broken on the upper-bound path.

Indeed, that's a silly bug, not sure how I could have missed that. We are
currently in freeze for the upcoming minor releases but I have this staged to
go in directly after. Thanks for the report.

--
Daniel Gustafsson

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Paul A Jungwirth 2026-05-09 19:06:37 Re: bug: UPDATE FOR PORTION OF interact with updatable view
Previous Message Álvaro Herrera 2026-05-09 15:35:05 Re: Avoid unnecessary StringInfo allocation in tablesync COPY buffer