| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | zxwsbg(at)qq(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #18119: Failed assert while recoverying from pg_basebackup |
| Date: | 2023-09-20 22:34:24 |
| Message-ID: | ZQtzcH2lvo8leXEr@paquier.xyz |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2023-09-20 23:24:49 | Re: BUG #18057: unaccent removes intentional spaces |
| Previous Message | Tom Lane | 2023-09-20 14:25:12 | Re: BUG #17798: Incorrect memory access occurs when using BEFORE ROW UPDATE trigger |