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

From: Dave Cramer <davecramer(at)gmail(dot)com>
To: Austin Bonander <austin(dot)bonander(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 21:55:35
Message-ID: CADK3HH+Jo_qxDp8B6YJJVVOCRKQuPuH8rGLLeAzWvFMBdmLLyA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 20 May 2026 at 18:21, Austin Bonander <austin(dot)bonander(at)gmail(dot)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(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
>>
>
Using Claude I have created another patch which calls out all
signed/unsigned
see attached

Attachment Content-Type Size
0001-doc-clarify-unsigned-integer-fields-in-protocol-messages.patch application/octet-stream 9.3 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message surya poondla 2026-05-21 22:09:05 Re: pg_rewind does not rewind diverging timelines
Previous Message Andreas Karlsson 2026-05-21 21:22:31 Re: Prevent setting NO INHERIT on partitioned not-null constraints