| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Mohan Nagandlla <nagandllamohan(at)gmail(dot)com> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #17093: invalid primary checkpoint record |
| Date: | 2021-07-12 06:53:35 |
| Message-ID: | YOvm78B+GrMxjm3D@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2021-07-12 08:00:16 | BUG #17100: undefined reference to `pg_qsort and pq_xxx |
| Previous Message | Mohan Nagandlla | 2021-07-12 05:36:23 | Re: BUG #17093: invalid primary checkpoint record |