| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: 2026-08-13 release announcement draft |
| Date: | 2026-08-10 01:30:36 |
| Message-ID: | 1784405.1786325436@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Jonathan S. Katz" <jkatz(at)postgresql(dot)org> writes:
> What do you think of this framing:
> ===
> This update fixes over 110 bugs that were reported in the last several
> months.
> This specific issue only affects PostgreSQL 14, 15, and 16, but we're
> highlighting it in the release announcement due to its severity:
> * Fix a self-deadlock that could occur while replaying WAL generated by
> an older minor version. This regression, introduced in the previous set
> of minor releases, could cause a standby server following a primary
> running an older minor version to become stuck.
> The remainder of issues listed below affect PostgreSQL 18. Some of these
> issues may also affect other supported versions of PostgreSQL.
> ...
> ==
WFM, though personally I'd be more assertive in that last sentence:
"Many of these issues also affect older versions of PostgreSQL."
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2026-08-10 02:15:53 | Re: CREATE SUBSCRIPTION ... SERVER vs. pg_dump, etc. |
| Previous Message | Jonathan S. Katz | 2026-08-10 00:53:20 | Re: 2026-08-13 release announcement draft |