Request a Demo
Home   >   mailing lists

Re: Startup PANIC on standby promotion due to zero-filled WAL segment - Mailing list pgsql-hackers

From Alena Vinter
Subject Re: Startup PANIC on standby promotion due to zero-filled WAL segment
Date
Msg-id CAGWv16+9r8roFdReY1qV6rcFDi9UdzmjQc+GfKbdvHZMomCqCg@mail.gmail.com
Whole thread Raw
In response to Re: Startup PANIC on standby promotion due to zero-filled WAL segment  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
Tree view
I like the idea of preventing promotion to avoid such failures -- it sounds reasonable.

However, we still have the problem: if the standby is stopped with non-replicated TLI 2, it will fail to start:
"FATAL: according to history file, WAL location Y belongs to timeline X, but previous recovered WAL file came from timeline X+1". 
This happens even if no promotion is attempted — just a plain restart of the standby. So the issue isn’t only about when to allow promotion.

Regarding my proposed solution: could you clarify why it isn’t correct? I’d appreciate more detail so I can address your concerns.

---
Alena Vinter
Attachment

pgsql-hackers by date:

Previous
From: Dilip Kumar
Date:
Subject: Re: Proposal: Conflict log history table for Logical Replication
Next
From: Konstantin Knizhnik
Date:
Subject: Re: index prefetching