| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Draft back-branch release notes are up |
| Date: | 2026-11-06 20:19:30 |
| Message-ID: | CAH2-WznLZds0-5yQP2HTNy-dnb21BBf2oxgbMzVPnNyGstYaEw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Nov 6, 2026 at 2:47 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> As usual, please send comments/corrections by Sunday.
I noticed a couple of small issues for "Fix snapshot export and import
to work properly on a snapshot taken during recovery":
* The release notes should credit Bertrand Drouvot as an additional
author of the fix.
* Seems worth pointing out that this problem is associated with
running pg_dump with multiple jobs (--jobs=N) on a standby [1]. It
might also be worth mentioning that it requires the subxact cache on
the primary to overflow.
I am 100% sure that this bug has real world relevance (unlike all of
the other corruption bugs I worked on for this release). It hit at
least a handful of users, causing alarming misbehavior on affected
standbys. That's why I'm being particular about how it gets presented.
[1] https://postgr.es/m/17846-1a0e5ce976f4c01a@postgresql.org
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2026-11-06 20:34:32 | Re: Draft back-branch release notes are up |
| Previous Message | Cagri Biroglu | 2026-11-06 20:07:22 | Re: Per-table resync for logical replication subscriptions |