Re: Bug: PG 14 recovery failure

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: David Rowley <dgrowleyml(at)gmail(dot)com>
Cc: Torsten Förtsch <tfoertsch123(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org>
Subject: Re: Bug: PG 14 recovery failure
Date: 2026-02-19 04:11:43
Message-ID: aZaNfzFI7FLPv9cc@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Feb 18, 2026 at 11:27:37PM +1300, David Rowley wrote:
> On Wed, 18 Feb 2026 at 21:40, Torsten Förtsch <tfoertsch123(at)gmail(dot)com> wrote:
>> 2026-02-14 01:53:59.595 UTC [2441074] LOG: restored log file "0000000500017F8D0000004E" from archive 2026-02-14 01:53:59.605 UTC [2441074] FATAL: could not access status of transaction 2030956544
>
> There's a planned out-of-cycle release to fix this. See [1].

In more details, here is the specific fix in the v14~18 range:
https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=817f74600d0d

And its related thread:
https://www.postgresql.org/message-id/20260214090150.GC2297@p46.dedyn.io;lightning.p46.dedyn.io
--
Michael

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Peter Eisentraut 2026-02-19 14:48:33 Re: Can we get sha* function over text, that could be used in index?
Previous Message Nico Heller 2026-02-18 21:19:36 Re: Guarantee order of batched pg_advisory_xact_lock