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 1ubbPR-002t0r-8E for pgpool-hackers@arkaria.postgresql.org; Tue, 15 Jul 2025 08:53:09 +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 1ubbPP-000XeF-BY for pgpool-hackers@arkaria.postgresql.org; Tue, 15 Jul 2025 08:53:07 +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.94.2) (envelope-from ) id 1ubbPP-000Xe7-61 for pgpool-hackers@lists.postgresql.org; Tue, 15 Jul 2025 08:53:07 +0000 Received: from meldrar.postgresql.org ([2a02:c0:301:0:ffff::31]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1ubbPN-007NWX-1K for pgpool-hackers@lists.postgresql.org; Tue, 15 Jul 2025 08:53:06 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Content-Transfer-Encoding:Content-Type: Mime-Version:References:In-Reply-To:From:Subject:To:Message-Id:Date:Sender: Reply-To:Cc:Content-ID:Content-Description; bh=nP5iV1QprcVoN2J3pQCESQdi32WFUs/oseTEuDQxlCM=; b=mgy89V1aY55MEi2qT4p8h0/Zec EW8itbKhf1wZ+W+s237CYiB1LUp08rf2BQlUeUgCk4iIN9biZ+za2G6Kau68h40RoJWWT6jYgbF2e TqJdlsJTwkN4MtB+qOcM77WiJxEct13sHdNrswFI+cmvV7foWXTcj3x5FiTOe5MhqmiQ6pWQIQpKF /UgjAiK3QFwk34KvHMyr7wuvbIwAokoCdVgM+H6UMHp2PWGHiqh4HIeq7tUdR2nwu3qIh021Ir082 JxMiIyZj8i8KWcKO4BgXQ/+yb6nrdOJdqhYfwR1mDJIitV9d1N0G1KnE9vRKMdcAmS1FD7O/7qEeD 39Ybc0/w==; Received: from [2409:11:4120:300:2c38:4ebf:6c24:c2e8] (helo=localhost) by meldrar.postgresql.org with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 (Exim 4.96) (envelope-from ) id 1ubbPJ-00Ab3q-2k for pgpool-hackers@lists.postgresql.org; Tue, 15 Jul 2025 08:53:04 +0000 Date: Tue, 15 Jul 2025 17:52:53 +0900 (JST) Message-Id: <20250715.175253.2268867545355726159.ishii@postgresql.org> To: pgpool-hackers@lists.postgresql.org Subject: Re: Implement protocol 3.2 BackendKeyData and cancel request message From: Tatsuo Ishii In-Reply-To: <20250715.143408.2248698006180584277.ishii@postgresql.org> References: <20250714.155710.1706961744888449986.ishii@postgresql.org> <20250715.105440.1906014753922388607.ishii@postgresql.org> <20250715.143408.2248698006180584277.ishii@postgresql.org> X-Mailer: Mew version 6.8 on Emacs 26.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Host-Lookup-Failed: Reverse DNS lookup failed for 2409:11:4120:300:2c38:4ebf:6c24:c2e8 (failed) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk >>> Starting from PostgreSQL 18, frontend/backend protocol has been >>> changed from 3.0 to 3.2. In the changes the BackendKeyData and query >>> cancel message are modified to allow variable length cancel key. >>> >>> This commit is a follow up to 766e73811 and implements the changes >>> needed above. See attached patches. >>> >>> With the patch we can connect to PostgreSQL 18 frontend and backend >>> using 3.2 protocol. >>> >>> Since PostgreSQL 18's psql uses 3.0 protocol by default, in order to >>> test 3.2 protocol, you can do something like: >>> >>> PGMAXPROTOCOLVERSION="3.2" psql -p 11000 test >> >> Attached is the v2 patch which add more comments and some cosmetic >> changes. > > Attached is the v3 patch which fixes a compiler error. V3 patch pushed to master branch. Thanks. -- Tatsuo Ishii SRA OSS K.K. English: http://www.sraoss.co.jp/index_en/ Japanese:http://www.sraoss.co.jp