Re: 12.2: Why do my Redo Logs disappear??

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Peter <pmc(at)citylink(dot)dinoex(dot)sub(dot)org>
Cc: "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: 12.2: Why do my Redo Logs disappear??
Date: 2020-06-09 00:40:20
Message-ID: CAH2-WzkW4deJz2WfwAw5LuK+s_nKHJkfA4WxXYS+OObnQ47jYA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Jun 8, 2020 at 5:17 PM Peter <pmc(at)citylink(dot)dinoex(dot)sub(dot)org> wrote:
> Loosing a RedoLog is very bad, because there is no redundancy,
> loosing a single one of them makes the timeline disappear and it
> will only reappear after another Base Backup. Very very bad.

> In this case, it seems, Postgres will delete the current log
> without archiving it. :(

I strongly suspect that you were hit by the bug fixed in commit
4e87c483. You should upgrade to Postgres 12.3 ASAP, to get that fix:

"Avoid premature recycling of WAL segments during crash recovery
(Jehan-Guillaume de Rorthais)

WAL segments that become ready to be archived during crash recovery
were potentially recycled without being archived."

Sorry that you were affected by this bug -- it really sucks.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Thomas Munro 2020-06-09 00:41:13 Re: troubleshooting postgresql ldap authentication
Previous Message Adrian Klaver 2020-06-09 00:35:40 Re: 12.2: Why do my Redo Logs disappear??