| From: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
|---|---|
| To: | Dave Cramer <davecramer(at)gmail(dot)com> |
| 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 10:17:57 |
| Message-ID: | CAGECzQQqcMsZEYu9jxcov-aiXfKfyuXg6heO8mP9fJXHZWCnSQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2025-05-29 11:12:27 | Re: Correct documentation for protocol version |
| Previous Message | Nisha Moond | 2025-05-29 09:00:41 | Re: Fix slot synchronization with two_phase decoding enabled |