Re: Correct documentation for protocol version

Dave Cramer <davecramer@gmail.com>

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-06-27T11:20:38Z
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, 26 Jun 2025 at 18:04, Jelte Fennema-Nio <postgres@jeltef.nl> wrote:

> On Fri, 30 May 2025 at 11:00, Jelte Fennema-Nio <postgres@jeltef.nl>
> wrote:
> > If we decide to keep it I think it would be best to have all protocol
> > changes on a single page. I'd just put the changes from 2.0 to 3.0 at
> > the bottom of the page.
>
> Attached are my proposed changes which split this page into different
> sections, one for each protocol version, with the most recent protocol
> changes at the top.
>

Thanks Jelte,

Looks good to me


Dave Cramer