From: | Dave Cramer <davecramer(at)gmail(dot)com> |
---|---|
To: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
Cc: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Correct documentation for protocol version |
Date: | 2025-05-29 11:12:27 |
Message-ID: | CADK3HH+i_MLHLZ4VCdEeb66JuwYm4Yx3dG7NLWZ3bcjhKHSxoQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, 29 May 2025 at 06:18, Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> wrote:
> On Thu, 29 May 2025 at 00:29, Dave Cramer <davecramer(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2025-05-29 11:14:05 | Re: Warning -Wclobbered in PG_TRY(...) |
Previous Message | Jelte Fennema-Nio | 2025-05-29 10:17:57 | Re: Correct documentation for protocol version |