Re: Patch for bind message regarding the number of parameters and result column format codes - Mailing list pgsql-hackers

From Austin Bonander
Subject Re: Patch for bind message regarding the number of parameters and result column format codes
Date
Msg-id CADcQg=W4Vfq5yzq88hVcFK3A_+uGjpwLbxxLLUm-o-kGQa5XiQ@mail.gmail.com
Whole thread
In response to Patch for bind message regarding the number of parameters and result column format codes  (Dave Cramer <davecramer@gmail.com>)
List 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://www.postgresql.org/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@gmail.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

pgsql-hackers by date:

Previous
From: Peter Smith
Date:
Subject: Re: Proposal: Conflict log history table for Logical Replication
Next
From: Chao Li
Date:
Subject: Re: Set notice receiver before libpq connection startup