| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Nikolay Samokhvalov <nik(at)postgres(dot)ai> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: [PATCH] Doc: clarify that pg_upgrade statistics transfer works cross-version |
| Date: | 2026-03-26 02:33:42 |
| Message-ID: | CAKFQuwYmspFfkno8Xf_RL4C5AQFDgvSXRcg5kmofrRy=cz88jw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Wednesday, March 25, 2026, Nikolay Samokhvalov <nik(at)postgres(dot)ai> wrote:
>
> If you don't know anything about implementation, it is natural to
> expect that something new will work only when both old and new
> clusters support it.
>
>
But we don’t call out “new features” in the documentation. Just
“features”. And so when the pg_upgrade docs says “pg_upgrade supports
upgrades from 9.2.X and later” then unless there is a note to the contrary
(which there is not here) that applies to everything pg_upgrade does.
Put differently, read the docs as if you were unaware in which version that
capability was introduced. This is the style/assumption the documentation
is written in/using.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Boris Mironov | 2026-03-29 05:37:47 | Request for cleaner explanation of default_toast_compression parameter |
| Previous Message | Nikolay Samokhvalov | 2026-03-26 01:13:23 | Re: [PATCH] Doc: clarify that pg_upgrade statistics transfer works cross-version |