Make mesage at end-of-recovery less scary.

From: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Make mesage at end-of-recovery less scary.
Date: 2020-02-28 07:01:00
Message-ID: 20200228.160100.2210969269596489579.horikyota.ntt@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello, this is a followup thread of [1].

# I didn't noticed that the thread didn't cover -hackers..

When recovery of any type ends, we see several kinds of error messages
that says "WAL is broken".

> LOG: invalid record length at 0/7CB6BC8: wanted 24, got 0
> LOG: redo is not required
> LOG: database system is ready to accept connections

This patch reduces the scariness of such messages as the follows.

> LOG: rached end of WAL at 0/1551048 on timeline 1 in pg_wal during crash recovery
> DETAIL: invalid record length at 0/1551048: wanted 24, got 0
> LOG: redo is not required
> LOG: database system is ready to accept connections

[1] https://www.postgresql.org/message-id/20200117.172655.1384889922565817808.horikyota.ntt%40gmail.com

I'll register this to the coming CF.

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center

Attachment Content-Type Size
0001-Make-End-Of-Recovery-error-less-scary.patch text/x-patch 3.1 KB

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andy Fan 2020-02-28 07:02:28 Re: Trying to pull up EXPR SubLinks
Previous Message Michael Paquier 2020-02-28 06:43:57 Re: [Patch] pg_rewind: options to use restore_command from recovery.conf or command line