Re: BUG #18119: Failed assert while recoverying from pg_basebackup - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: BUG #18119: Failed assert while recoverying from pg_basebackup
Date
Msg-id ZQtzcH2lvo8leXEr@paquier.xyz
Whole thread Raw
In response to BUG #18119: Failed assert while recoverying from pg_basebackup  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
On Wed, Sep 20, 2023 at 01:12:52PM +0000, PG Bug reporting form wrote:
> This problem was first found in PG 15, see following link for details:
>
https://www.postgresql.org/message-id/flat/20230227.120101.1600358770821352577.horikyota.ntt%40gmail.com#65fe5aea5862c8196a4ade348c71fde9
>
> And it still exists in PG 16.

Missing a recovery.signal prevents the startup process from
initializing some structures that may be required once consistency is
reached, in this case some of the facility for standby snapshots.
I've sent a patch about that, as well:
https://commitfest.postgresql.org/44/4244/

The problem is much older than the addition of checkpoints run during
crash recovery.
--
Michael

Attachment

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #17798: Incorrect memory access occurs when using BEFORE ROW UPDATE trigger
Next
From: Michael Paquier
Date:
Subject: Re: BUG #18057: unaccent removes intentional spaces