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

From Dave Cramer
Subject Re: Patch for bind message regarding the number of parameters and result column format codes
Date
Msg-id CADK3HH+Jo_qxDp8B6YJJVVOCRKQuPuH8rGLLeAzWvFMBdmLLyA@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


On Wed, 20 May 2026 at 18:21, Austin Bonander <austin.bonander@gmail.com> wrote:
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

Using Claude I have created another patch which calls out all signed/unsigned 
see attached
Attachment

pgsql-hackers by date:

Previous
From: Andreas Karlsson
Date:
Subject: Re: Prevent setting NO INHERIT on partitioned not-null constraints
Next
From: surya poondla
Date:
Subject: Re: pg_rewind does not rewind diverging timelines