Re: Startup PANIC on standby promotion due to zero-filled WAL segment

From: Alena Vinter <dlaaren8(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Startup PANIC on standby promotion due to zero-filled WAL segment
Date: 2026-01-14 11:38:27
Message-ID: CAGWv16JP_DJfRnBPC+XomZPtgi+0KB7SZjULGH_5J6ZN9cTi4Q@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I revisited the issue and examined the problem and the proposed solution in
more depth. It’s now clear to me why the approach won’t work: if multiple
timelines are discovered at once (for example, if a replica is stopped, a
standby is promoted several times, and only then the replica resumes
replication), the current design may copy part of an earlier timeline from
the wrong predecessor into the current segment.

I’ll get back with a more correct solution soon. In the meantime,
suggestions are welcome!
---
Alena Vinter

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dilip Kumar 2026-01-14 11:39:26 Re: Proposal: Conflict log history table for Logical Replication
Previous Message Hayato Kuroda (Fujitsu) 2026-01-14 11:31:04 RE: Simplify code building the LR conflict messages