| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Ning Sun <classicning(at)gmail(dot)com>, pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: [PATCH] Correct the version sent in protocol negotiation |
| Date: | 2026-06-07 05:06:55 |
| Message-ID: | f3b25f9c1d383c37cb2d772b430e8ca5103905d2.camel@cybertec.at |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Sun, 2026-06-07 at 10:00 +0800, Ning Sun wrote:
> Our protocol doc describes protocol negotiation message will send latest
> minor version. However that field is a 4-byte one. The actual
> implementation sends full version including the major part:
>
> The patch included just clarifies this behavior by removing "minor" from
> "newest minor version".
To my understanding, the "minor version" is the entire version *including*
the last number, like 18.4 (and not only .4).
In this, I seem to be in agreement with
https://www.postgresql.org/support/versioning/
To me, removing the "minor" makes the text less clear. If we change that
at all, perhaps a wording like "the full version, including the minor
release" would remove any ambiguity.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ning Sun | 2026-06-07 07:40:37 | Re: [PATCH] Correct the version sent in protocol negotiation |
| Previous Message | Ning Sun | 2026-06-07 02:00:09 | [PATCH] Correct the version sent in protocol negotiation |