Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wibyV-000JT1-2v for pgsql-docs@arkaria.postgresql.org; Sat, 11 Jul 2026 17:58:52 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wibyU-004gsg-0k for pgsql-docs@arkaria.postgresql.org; Sat, 11 Jul 2026 17:58:50 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wiYde-0042fq-2V for pgsql-docs@lists.postgresql.org; Sat, 11 Jul 2026 14:25:07 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wiYdd-00000000Bwe-2By0 for pgsql-docs@lists.postgresql.org; Sat, 11 Jul 2026 14:25:06 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:Cc:From:To:Subject: Content-Transfer-Encoding:MIME-Version:Content-Type:Sender:Content-ID: Content-Description:In-Reply-To:References; bh=i1beNe2yakMZWABn4Qg6DstTjdxdiwHheNJAIFrIo+Q=; b=fg7cQiUn5EZd24C1b+3qJT5jJs GBj0WN3VzL9b1R0MVculJpiKUc+oQK4o8AC37zP09PQekfz0oqUFGTsthIy2GahpyC+lnJsvwI3Mg C12TAS+t3mn/xm/uzSeLjso7iyigdU8/EmaeIrGha/reUsUhuOASoW1Ni983ijn4A2iYF33UYDqC8 LBUltaw5aDdFTcQODmC/u9SYr0jFOUelprK8bmYbDsNG0UP1bEXoK+fmbnfhWIfjSVWLXdH7LSdr4 zm5g7AE1VNqRJwE3IoJD/zIUQr1ZGoHN559RgnpjR1jxUK/q7ENgeV2cDMexVmla3276aoqHowAlr yGCObOHg==; Received: from wrigleys.postgresql.org ([2a02:16a8:dc51::60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wiYdc-000dGC-2v for pgsql-docs@lists.postgresql.org; Sat, 11 Jul 2026 14:25:05 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wiYdZ-004wIG-1y for pgsql-docs@lists.postgresql.org; Sat, 11 Jul 2026 14:25:02 +0000 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: Postgres Protocol Message Formats Clarification To: pgsql-docs@lists.postgresql.org From: PG Doc comments form Cc: akindipejohn2017@gmail.com Reply-To: akindipejohn2017@gmail.com, pgsql-docs@lists.postgresql.org Date: Sat, 11 Jul 2026 14:24:07 +0000 Message-ID: <178377984700.881008.10843696440740337042@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/18/protocol-message-formats.html Description: While the docs correctly state here (https://www.postgresql.org/docs/current/protocol-overview.html#PROTOCOL-ME= SSAGE-CONCEPTS) that the size bytes represent the length of the message except the first byte (the msg type byte), this page (https://www.postgresql.org/docs/current/protocol-message-formats.html#PROT= OCOL-MESSAGE-FORMATS) which explicitly describes the message formats does not include this clarification. Readers who come across this page without reading the protocol overview page will be quite confused should they try to implement the protocol and see short by one message sizes. I propose that this clarification be more explicitly added to the message formats page to avoid confusing readers.