Horton

Re: Correct documentation for protocol version

Dave Cramer <davecramer@gmail.com>

View thread
From: Dave Cramer <davecramer@gmail.com>
To: Jelte Fennema-Nio <postgres@jeltef.nl>
Cc: Fujii Masao <masao.fujii@oss.nttdata.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-05-29T11:12:27Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Do not hardcode PG_PROTOCOL_LATEST in NegotiateProtocolVersion

On Thu, 29 May 2025 at 06:18, Jelte Fennema-Nio <postgres@jeltef.nl> wrote:

> On Thu, 29 May 2025 at 00:29, Dave Cramer <davecramer@gmail.com> wrote:
> > I found another place where the docs should be updated. The Changes
> since Protocol 2.0
>
> I think it makes sense to have a dedicated page like this that lists
> any protocol changes that we do. But I think the current structure
> doesn't make much sense anymore. I expect no-one to upgrade a client
> from protocol 2.0 anymore. So I'd replace this page with a new one
> with the following structure
>
> # Summary of protocol changes over time
>
> ## Protocol changes in version 3.2
>
> - Longer cancel key messages
>
> ## Protocol changes to 3.0 without protocol version bump
>
> - NegotiateProtocolVersion in 9.?
> - Direct SSL negotiation in PG17
>

Agreed that nobody upgrades a client from 2.0 but is there value in keeping
the history ?

Perhaps another section which would be "Changes in 3.x" ?

Dave