Re: BUG #19897: Recovery fails after "LOG: consistent recovery state reached"

From: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19897: Recovery fails after "LOG: consistent recovery state reached"
Date: 2026-11-15 16:15:02
Message-ID: CAN4CZFOFW=Kq54Udyb-LUzu++a+2=F+=CVf5nXnNTdR5RWXJHw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

And after thinking about these changes, I realized that both of our
patches broke standby promotion: both resulted in cases where we
promoted the standby when we shouldn't have.

The attached v3 now doesn't modify the logic when we have a primary
connection set, and contains both patches in one file instead.

Attachment Content-Type Size
v3-0001-Fix-immediate-recovery-targets-at-end-of-WAL.patch text/x-patch 14.5 KB

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message 민영재 2026-11-15 16:22:24 Re: BUG #19736: `JSON_OBJECT ... ABSENT ON NULL` accepts invalid keys when the value is NULL
Previous Message Joao Rito 2026-11-15 08:46:50 Re: BUG #19736: `JSON_OBJECT ... ABSENT ON NULL` accepts invalid keys when the value is NULL