Date: Tue, 15 Jul 2025 10:54:40 +0900 (JST)
Message-Id: <20250715.105440.1906014753922388607.ishii@postgresql.org>
To: pgpool-hackers@lists.postgresql.org
Subject: Re: Implement protocol 3.2 BackendKeyData and cancel request
 message
From: Tatsuo Ishii <ishii@postgresql.org>
In-Reply-To: <20250714.155710.1706961744888449986.ishii@postgresql.org>
References: <20250714.155710.1706961744888449986.ishii@postgresql.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed;
 boundary="--Next_Part(Tue_Jul_15_10_54_40_2025_664)--"
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/20250715.105440.1906014753922388607.ishii%40postgresql.org>
Precedence: bulk

----Next_Part(Tue_Jul_15_10_54_40_2025_664)--
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

> 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.

Best regards,
--
Tatsuo Ishii
SRA OSS K.K.
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp

----Next_Part(Tue_Jul_15_10_54_40_2025_664)--
Content-Type: Text/X-Patch; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="v2-0001-Feature-implement-protocol-version-3.2-BackendKey.patch"