Re: Postgresql error : PANIC: could not locate a valid checkpoint record

On Fri, Jun 24, 2022 at 01:03:57PM +0000, Mahendrakar, Prabhakar - Dell Team wrote:
> Is it possible to explicitly issue a checkpoint before we move on to
> the pg_upgrade command?
> so that in the circumstances of the Upgrade issues (like PANIC:
> could not locate a valid checkpoint record), we still have this
> last explicit checkpoint available.
>
> Please let us know your thoughts on this.

Well, you have mentioned the use of pg_upgrade, but you are giving
zero details about what kind of command you used, how you handled
the clusters before and after that were upgraded, or what kind of
environment is getting used. With this little amount of details,
nobody will be able to guess what's happening. This issue could also
be caused by the environment. For example, it is possible in some
carelessly-setup enviromnents that a flush is issued and recognized as
completed by the OS, and thought as completed by Postgres, but an
application layer between the OS and the actual hardware did not issue
the flush (be it an OS, FS, disk or a VM-related thing), which would
make this issue reachable.
--
Michael