| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Peter Smith <smithpb2250(at)gmail(dot)com>, Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: DOCS - Clarify the publication 'publish_via_partition_root' default value. |
| Date: | 2025-12-17 21:08:53 |
| Message-ID: | CAKFQuwbtUAx-ZaW1aN=z796NEsPuA2-JacMGrMNxfuZH8JpADg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wednesday, December 17, 2025, Jacob Champion <
jacob(dot)champion(at)enterprisedb(dot)com> wrote:
> On Wed, Dec 17, 2025 at 4:04 AM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
> wrote:
> > LGTM. As this is not any bug fix rather a text improvement, so it is
> > good to fix this in HEAD only.
>
> Don't we typically backpatch documentation improvements? Otherwise no
> one gets the better docs for a year.
>
Presently it’s the same criteria as for the code - things deemed bug fixes
get back-patched; pure enhancements do not.
I doubt we’d want to push them back beyond the latest stable release but
there is definitely an argument for new efforts to be dropped into there
and not just master.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-12-17 21:09:46 | Re: Fixing the btree_gist inet mess |
| Previous Message | Euler Taveira | 2025-12-17 20:49:03 | Re: Improve logical replication usability when tables lack primary keys |