Yes, We are using the pg_upgrade utility of Postgres. From: Mateusz Henicz <mateuszhen...@gmail.com> Sent: Friday, June 17, 2022 3:31 PM To: Mahendrakar, Prabhakar - Dell Team Cc: pgsql-general@lists.postgresql.org Subject: Re: Postgresql error : PANIC: could not locate a valid checkpoint record
[EXTERNAL EMAIL] Hi, Have you done pg_upgrade post Postgres 13 installation? https://www.postgresql.org/docs/13/pgupgrade.html [postgresql.org]<https://urldefense.com/v3/__https:/www.postgresql.org/docs/13/pgupgrade.html__;!!LpKI!idvJ795EwLEkEftyMMQc6j4AvHBN-AWOsHhukZYHV0VBPR8PRtDCRs_JDRGs5Nz34Vs4VK05szBLxdJ13Wzjztu6q67YUhUY$> Cheers, Mateusz pt., 17 cze 2022 o 11:20 Mahendrakar, Prabhakar - Dell Team <prabhakar.mahendr...@dellteam.com<mailto:prabhakar.mahendr...@dellteam.com>> napisaĆ(a): Hello, Good Morning ! We are facing checkpoint related issues from PostGreSQL 13.4 ( could not locate a valid checkpoint record) and Postgres service fails to come up. ======================================================================================================== LOG: starting PostgreSQL 13.4 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-16), 64-bit LOG: listening on IPv4 address "127.0.0.1", port 9003 LOG: listening on IPv4 address "10.xx.xx.x..", port 9003 LOG: listening on Unix socket "/tmp/.s.PGSQL.9003" LOG: database system was shut down at 2022-06-09 10:19:24 CEST LOG: invalid primary checkpoint record PANIC: could not locate a valid checkpoint record LOG: startup process (PID 8773) was terminated by signal 6: Aborted LOG: aborting startup due to startup process failure LOG: database system is shut down This issue is seen in both Windows and Linux OS platforms. To Brief on the Scenario: Our product say example with Version A1 uses Postgres 10 and in the latest version of our product (Say A2) we upgraded the Postgres to 13. When we try to upgrade our Product through InstallAnyWhere from A1 to A2, Postgres service fails with above mentioned error. Could you please suggest the probable cause of the issue. Let us know if you require any more information. Thanks, Prabhakar Internal Use - Confidential Internal Use - Confidential