public inbox for [email protected]
help / color / mirror / Atom feedFrom: David Steele <[email protected]>
To: Michael Paquier <[email protected]>
Cc: Pg Hackers <[email protected]>
Subject: Re: Add checkpoint/redo LSNs to recovery errors.
Date: Sun, 10 Mar 2024 16:58:19 +1300
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
On 2/29/24 16:42, Michael Paquier wrote:
> On Thu, Feb 29, 2024 at 10:53:15AM +1300, David Steele wrote:
>> This patch adds checkpoint/redo LSNs to recovery error messages where they
>> may be useful for debugging.
>
> I've scanned a bit xlogrecovery.c, and I have spotted a couple of that
> could gain more information.
>
> ereport(PANIC,
> (errmsg("invalid redo record in shutdown checkpoint")));
> [...]
> ereport(PANIC,
> (errmsg("invalid redo in checkpoint record")));
> These two could mention CheckPointLoc and checkPoint.redo.
>
> ereport(PANIC,
> (errmsg("invalid next transaction ID")));
> Perhaps some XID information could be added here?
>
> ereport(FATAL,
> (errmsg("WAL ends before consistent recovery point")));
> [...]
> ereport(FATAL,
> (errmsg("WAL ends before end of online backup"),
>
> These two are in xlog.c, and don't mention backupStartPoint for the
> first one. Perhaps there's a point in adding some information about
> EndOfLog and LocalMinRecoveryPoint as well?
For now I'd like to just focus on these three messages that are related
to a missing backup_label or a misconfiguration of restore_command when
backup_label is present.
No doubt there are many other recovery log messages that could be
improved, but I'd rather not bog down the patch.
Regards,
-David
view thread (3+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Add checkpoint/redo LSNs to recovery errors.
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox