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.94.2) (envelope-from ) id 1v6AEx-000Gq9-Gs for pgsql-docs@arkaria.postgresql.org; Tue, 07 Oct 2025 16:08:39 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1v6AEv-0017f7-8T for pgsql-docs@arkaria.postgresql.org; Tue, 07 Oct 2025 16:08:38 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1v6AEv-0017ez-0o for pgsql-docs@lists.postgresql.org; Tue, 07 Oct 2025 16:08:37 +0000 Received: from mail-ed1-x535.google.com ([2a00:1450:4864:20::535]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1v6AEt-000t2p-1w for pgsql-docs@lists.postgresql.org; Tue, 07 Oct 2025 16:08:37 +0000 Received: by mail-ed1-x535.google.com with SMTP id 4fb4d7f45d1cf-636de696e18so10802190a12.3 for ; Tue, 07 Oct 2025 09:08:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1759853314; x=1760458114; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=Qn5ECbEddR9pxCRRavYkhPpWEtfjzL1vPfVfrYtJz7s=; b=dhnVmtxYXbc7Ke9m3iJ0LJtQkyeLN+mxL6XmQZLqaYoevG/i6qGVI6HEKjdfHox0m6 SanXoFvG+ZVj6RDcGXrZAq/l9T+uFj1RYE2Bf6mbc1tqs7uAgw4EGdZakG6Fo/Ce/drD 5G3jet9aWd0r8klXfoAP9/FYmYGe9Eemg1XqAc21Uc+PwF1UZI6mhzZvyDkoLiBdHrYL LvbJlLM5rJ+uz/m4HrJPQueTwkau/T3CdjJN+D4J9sphfok+jkewFF/yFtitcMJxBIRI cO/CSXZHIfOrFBPiJreL1QKn88fic3q1Ww3A9xaOK5W7AO9m3S+oourAvUUqto6qBM/V U+aQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1759853314; x=1760458114; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=Qn5ECbEddR9pxCRRavYkhPpWEtfjzL1vPfVfrYtJz7s=; b=IqoPGW8WG51DwCdDW0KEpinFbPy6IL70SMLO/bwCjrIXaL/Jn+CKXuPqqx4dzRtmRL 5wDUFGRkcUf+D1/aqmTa6gE6cAcVPcJQb2Yu9PMlwD40tzZhTQyZpFd485OgWawzWxog UULFoVNMm1FyzD8mLA+QptxlYnWuP51MI+RbffDnZPOtKRpI8R05XwWxhXvW6m+fNQP4 +4oIGvz89Xy1SemMGS38qZqI49XrlydcmgAwGPktOBqiwmcwA4NLN61TGMK4QPAf0CFa PCWQs6FzI/KmJJzM2M8iDb2ZDtbRBOiVaWjY7E9M5sp2P6IAaRA1RqqQdfl+MEcVJj+0 lFWA== X-Gm-Message-State: AOJu0YwndQKAtO9jolxGy8ryJWK62eGEzzDnKh/gBL9g85cDZLzHgAcY RnqRTFHGHuDfshUfL+eF2TCGXH78fWTNUCeqlnVU45QderJUUe3ImSUsMeACUtI8CYW6LPX65+9 oNvZwsGYl7McvgosUsoC35wpqiOUNbZSKswwvyS0= X-Gm-Gg: ASbGncuHQpLPEjUqRxU38L7uFI4uh75XowSJHefdkdQ5EBG9AWytlj0M+md9cUzfM7Q nwfsLAlAvO1gU+JKwgrVMtw4hlxvb6+gAj00iK0j6vBsJP2ReRm18GlUNXLw9GqlZZIB48nB2sb +liwQH0dbem8mtrEOUN7czPXahwySY6GXSOpeCFapWlvhf5Sywp/40ey0ywMz6gAkaZC20g0aNn HvmEf6oPPTMfF4M+abgQ5fVFOATbjKc X-Google-Smtp-Source: AGHT+IHPIdPTrZ6TVH0H+hKtbg61mH9MRePFxHcCNgRPYl2wKeJA9gmLIGD0ZUHAhpkfi6i1Y2FRy8n9l+RYQALzOZk= X-Received: by 2002:a05:6402:5187:b0:634:5705:5705 with SMTP id 4fb4d7f45d1cf-639348de132mr17254140a12.12.1759853313441; Tue, 07 Oct 2025 09:08:33 -0700 (PDT) MIME-Version: 1.0 From: Dmitry Igrishin Date: Tue, 7 Oct 2025 19:08:22 +0300 X-Gm-Features: AS18NWDbO63GKVC9g4tT5qDvmvvkNM1TQTIEz9ijyr0gz9Y1GG__afi7aj2wVQ4 Message-ID: Subject: CancelRequest(F) documentation. To: pgsql-docs@lists.postgresql.org Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hello, CancelRequest(F) documentation at https://www.postgresql.org/docs/18/protocol-message-formats.html#PROTOCOL-MESSAGE-FORMATS-CANCELREQUEST seems to be inconsistent for protocol 3.2. It is stated here that the length of the message is always 16 bytes (specified as Int32(16)), however the maximum message length actually depends on the secret key length (which can be up to 256 bytes, as also stated in the documentation.) I would propose to specify the overall message length as Int32 in the documentation for PostgreSQL 18+. Thanks.