Search Postgresql Archives

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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello there,

Please find my response below

> You should not be using 13.4, but the latest minor release, at this point 13.7.
        May be in the near future we would migrate to 13.7 and not now at present.

> Anyway, the error message looks like somebody removed the contents of the "pg_wal"
directory.  How exactly did you upgrade PostgreSQL?
	We are using the pg_upgrade utility for doing the upgrade.

Thanks,
Prabhakar


Internal Use - Confidential

-----Original Message-----
From: Laurenz Albe <laurenz.albe@xxxxxxxxxxx> 
Sent: Friday, June 17, 2022 4:10 PM
To: Mahendrakar, Prabhakar - Dell Team; pgsql-general@xxxxxxxxxxxxxxxxxxxx
Subject: Re: Postgresql error : PANIC: could not locate a valid checkpoint record


[EXTERNAL EMAIL] 

On Fri, 2022-06-17 at 06:35 +0000, Mahendrakar, Prabhakar - Dell Team wrote:
> 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.

You should not be using 13.4, but the latest minor release, at this point 13.7.

Anyway, the error message looks like somebody removed the contents of the "pg_wal"
directory.  How exactly did you upgrade PostgreSQL?

Yours,
Laurenz Albe
--
Cybertec | https://urldefense.com/v3/__https://www.cybertec-postgresql.com__;!!LpKI!ihYHnSm7w4UDJHWNlSnVnxBN704J-jkctGZIQ9NPj3f9UeHxY5pPnRnpPcWN5mmrWxlXc9hVyRd8AkHaAPLaXuRtVz0WxIaDVoTQ$ [cybertec-postgresql[.]com]




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]

  Powered by Linux