Re: Fix logging for invalid recovery timeline
Benoit Lobréau <benoit.lobreau@dalibo.com>
From: Benoit Lobréau <benoit.lobreau@dalibo.com>
To: Michael Paquier <michael@paquier.xyz>, David Steele <david@pgbackrest.org>
Cc: "Andrey M. Borodin" <x4mmm@yandex-team.ru>,
Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2025-02-24T16:21:41Z
Lists: pgsql-hackers
Attachments
- V2_0001-Adjust-logging-for-invalid-recovery-timeline.patch (text/x-patch) patch 0001
On 2/24/25 2:05 AM, Michael Paquier wrote: > I think that you have the right idea here, avoiding the duplication > of the errdetail() which feels itchy when looking at the patch. Done this way in the attached patch. > This should have a note for translators that this field refers to a file > name. Is there a specific way todo this? -- Benoit Lobréau Consultant http://dalibo.com
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Improve FATAL message for invalid TLI history at recovery
- adc6032fa882 18.0 landed
-
Fix FATAL message for invalid recovery timeline at beginning of recovery
- 62bed7bb0f6c 15.13 landed
- b4969a29657d 16.9 landed
- 29cce279bbc5 17.5 landed
- 71f17823ba01 18.0 landed