| From: | Ning Sun <classicning(at)gmail(dot)com> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: [PATCH] Correct the version sent in protocol negotiation |
| Date: | 2026-06-07 07:40:37 |
| Message-ID: | 47ed4ed1-2d33-4e0d-afec-185ac75f43e4@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
I see. The "minor version" has its own meaning in postgres context.
That makes sense. Thank you for clarification, Laurenz.
On 07/06/2026 13:06, Laurenz Albe wrote:
> 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 | PG Doc comments form | 2026-06-08 07:42:45 | remark regarding 4.2.13. Row Constructors |
| Previous Message | Laurenz Albe | 2026-06-07 05:06:55 | Re: [PATCH] Correct the version sent in protocol negotiation |