Re: Patch for bind message regarding the number of parameters and result column format codes

From: Austin Bonander <austin(dot)bonander(at)gmail(dot)com>
To: Dave Cramer <davecramer(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Patch for bind message regarding the number of parameters and result column format codes
Date: 2026-05-21 01:20:48
Message-ID: CADcQg=W4Vfq5yzq88hVcFK3A_+uGjpwLbxxLLUm-o-kGQa5XiQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I appreciate the follow-up, Dave.

I hope this lands as-is, but for context here is the old thread I found
that suggested that the full document should be audited and disambiguated
for signed/unsigned:
https://stream.boxwatch.ru/message-id/20120901160523.GD2969%40momjian.us

Given the additional effort required, I can understand why this was left
unresolved for so long.

On Wed, May 20, 2026, 18:12 Dave Cramer <davecramer(at)gmail(dot)com> wrote:

> While talking to Austin he noted that the docs for the number of
> parameters is actually an unsigned integer.
>
> This patch corrects that.
>
> See
>
> 1. Parameter format codes count (line 4323) — read at postgres.c:1725
> 2. Parameter values count (line 4348) — read at postgres.c:1734
> 3. Result-column format codes count (line 4396) — read at postgres.c:2017
>
> Dave Cramer
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Chao Li 2026-05-21 02:09:25 Re: Set notice receiver before libpq connection startup
Previous Message Peter Smith 2026-05-21 01:19:18 Re: Proposal: Conflict log history table for Logical Replication