Re: Correct documentation for protocol version

From: "Jelte Fennema-Nio" <postgres(at)jeltef(dot)nl>
To: "Heikki Linnakangas" <hlinnaka(at)iki(dot)fi>
Cc: "Dave Cramer" <davecramer(at)gmail(dot)com>, "Fujii Masao" <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, "PostgreSQL Hackers" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "Jacob Champion" <jacob(dot)champion(at)enterprisedb(dot)com>
Subject: Re: Correct documentation for protocol version
Date: 2026-02-08 20:27:08
Message-ID: DG9V36JRMDGQ.1TVJEG5HZ8XEG@jeltef.nl
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 12 Aug 2025 at 11:52, Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> wrote:
> I had forgotten about that table. How about we simply remove this page
> completely and integrate the info about changes without a version bump
> into the table?

After Jacob made his changes to the "Protocol Versions" section in
e3d37853ecd, now seemed a good moment to update this patch to do the
proposed.

Attachment Content-Type Size
v2-0001-doc-Include-historical-protocol-changes-without-a.patch text/x-patch 2.0 KB
v2-0002-doc-Remove-Summary-of-Changes-since-Protocol-2.0.patch text/x-patch 5.7 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2026-02-08 21:26:41 Re: pg_upgrade: transfer pg_largeobject_metadata's files when possible
Previous Message Jelte Fennema-Nio 2026-02-08 19:05:57 Re: Don't use the deprecated and insecure PQcancel in our frontend tools anymore