Horton

Re: Correct documentation for protocol version

Jelte Fennema-Nio <postgres@jeltef.nl>

View thread
From: Jelte Fennema-Nio <postgres@jeltef.nl>
To: Dave Cramer <davecramer@gmail.com>
Cc: Fujii Masao <masao.fujii@oss.nttdata.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-05-30T09:00:33Z
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 13:12, Dave Cramer <davecramer@gmail.com> wrote:
> Agreed that nobody upgrades a client from 2.0 but is there value in keeping the history ?

Yeah, maybe.

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

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.