Re: Out-of-Cycle release? (was Re: BUG #19490: Streaming standby on 16.14 stops applying WAL on MultiXactOffsetSLRU when primary is 16.8)

Andrey Borodin <x4mmm@yandex-team.ru>

From: Andrey Borodin <x4mmm@yandex-team.ru>

To: Michael Banck <mbanck@gmx.net>

Cc: Heikki Linnakangas <hlinnaka@iki.fi>, j.karremans@jk-consult.nl, rmt@lists.postgresql.org, PostgreSQL mailing lists <pgsql-hackers@lists.postgresql.org>

Date: 2026-06-25T10:17:31Z

Lists: pgsql-bugs, pgsql-hackers


> On 25 Jun 2026, at 15:14, Andrey Borodin <x4mmm@yandex-team.ru> wrote:
> 
> WAL must be generated by 16.10
> or prior

Sorry for the noise, but WAL from 16.11 also can trigger this problem.


Best regards, Andrey Borodin.

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Fix self-deadlock when replaying WAL generated by older minor version
- 2bb60eb4feab 14 (unreleased) landed
- 2dfe75f9844f 15 (unreleased) landed
- 42a3194e5483 16 (unreleased) landed
Fix multixact backwards-compatibility with CHECKPOINT race condition
- 77dff5d937b1 16.14 cited
Don't reset 'latest_page_number' when replaying multixid truncation
- 23064542f8bd 16.13 cited
Set next multixid's offset when creating a new multixid
- 635166913078 16.12 cited