From: Michael Paquier <michael@paquier.xyz>
To: Mohan Nagandlla <nagandllamohan@gmail.com>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17093: invalid primary checkpoint record
Date: Mon, 12 Jul 2021 15:53:35 +0900
Message-ID: <YOvm78B+GrMxjm3D@paquier.xyz> (raw)
In-Reply-To: <CALSpdGn8c1QdNnwK3M_=40XsLqEUhpwbOaet3qdf_C1g-qk25g@mail.gmail.com>
References: <17093-3d9fd04cfa74d04a@postgresql.org>
<CALSpdGn8c1QdNnwK3M_=40XsLqEUhpwbOaet3qdf_C1g-qk25g@mail.gmail.com>
On Mon, Jul 12, 2021 at 11:06:23AM +0530, Mohan Nagandlla wrote:
> Hi team
> Any updates on this?
> Again my server crashed because of invalid chek point .
Your instance is, at short sight, corrupted, as the WAL segment
holding the checkpoint record looked at the beginning of recovery
should be flushed to disk. Please see here:
https://wiki.postgresql.org/wiki/Corruption
Also, note that using blindly pg_resetwal could cause corruptions in
many ways. On top of that, it may be something that is wrong in your
configuration. fsync = off could be an issue, for one. In short, it
is not really possible to say what's wrong without knowing more how
you are using PostgreSQL.
--
Michael
Attachments:
signature.asc (application/pgp-signature, 832B) download
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: pgsql-bugs@postgresql.org
Cc: michael@paquier.xyz, nagandllamohan@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17093: invalid primary checkpoint record
In-Reply-To: <YOvm78B+GrMxjm3D@paquier.xyz>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox