[PATCH] psql: Make ParseVariableDouble reject values above max

First seen: 2026-05-08 15:39:29+00:00 · Messages: 3 · Participants: 2

Latest Update

2026-05-20 · claude-opus-4-6

What's New

A single follow-up from Daniel Gustafsson confirming the fix has been committed and backpatched to v18. Key new data points:

  1. Commit is done. The fix has been pushed to the main branch and backpatched to v18 (the branch where WATCH_INTERVAL / ParseVariableDouble() was introduced). This resolves the thread.

  2. Test coverage added. Beyond the minimal one-line return false fix anticipated in prior analysis, Daniel notes the commit includes "a test for this behaviour" — meaning a regression test now exercises the upper-bound rejection path of ParseVariableDouble(), preventing future regressions if someone refactors the function.

  3. Backpatch scope narrower than speculated. Prior analysis suggested backpatching to "all supported branches that contain ParseVariableDouble()." The actual backpatch target is v18 only, which aligns with when WATCH_INTERVAL was introduced (PG18 development cycle, not PG17 as earlier speculated). This clarifies the feature's actual provenance.

The thread is now effectively closed — bug reported, diagnosed, confirmed, fixed, and committed within a short cycle.