postgresql error PANIC: could not locate a valid checkpoint record

by

It’s looking for a checkpoint record in the transaction log that probably doesn’t exist or is corrupted. You can determine if this is the case by running:

# Postgres >= 10
pg_resetwal DATADIR

# Postgres < 10
pg_resetxlog DATADIR

If the transaction log is corrupt, you’ll see a message like:

The database server was not shut down cleanly.  
Resetting the transaction log might cause data to be lost.  
If you want to proceed anyway, use `-f` to force reset.

You can then follow the instructions and run with -f to force the update:

# Postgres >= 10
pg_resetwal -f DATADIR

# Postgres < 10
pg_resetxlog -f DATADIR

That should reset the transaction log. However, it could leave your database in an indeterminate state as explained in the PostgreSQL documentation on pg_resetwal:

If pg_resetwal complains that it cannot determine valid data for
pg_control, you can force it to proceed anyway by specifying the
-f (force) option. In this case plausible values will be substituted
for the missing data. Most of the fields can be expected to match, but
manual assistance might be needed for the next OID, next transaction
ID and epoch, next multitransaction ID and offset, and WAL starting
location fields. These fields can be set using the options discussed
below. If you are not able to determine correct values for all these
fields, -f can still be used, but the recovered database must be
treated with even more suspicion than usual: an immediate dump and
reload is imperative. Do not execute any data-modifying operations in
the database before you dump, as any such action is likely to make the
corruption worse.

More Related Contents:

  1. PostgreSQL: Show tables in PostgreSQL
  2. PostgreSQL “DESCRIBE TABLE”
  3. PostgreSQL function for last inserted ID
  4. What are ‘$$’ used for in PL/pgSQL
  5. Adding ‘serial’ to existing column in Postgres
  6. Making sense of Postgres row sizes
  7. How to export table as CSV with headings on Postgresql?
  8. What’s the PostgreSQL datatype equivalent to MySQL AUTO INCREMENT?
  9. How to persist data in a dockerized postgres database using volumes
  10. Time zone names with identical properties yield different result when applied to timestamp
  11. Permission denied for relation
  12. CONSTRAINT to check values from a remotely related table (via join etc.)
  13. How do I get a column with consecutive, increasing numbers, without having any numbers missing?
  14. Can I automatically create a table in PostgreSQL from a csv file with headers?
  15. User defined variables in PostgreSQL
  16. PostgreSQL query very slow with limit 1
  17. How to add an auto-incrementing primary key to an existing table, in PostgreSQL?
  18. Postgres query optimization (forcing an index scan)
  19. psql: FATAL: database “” does not exist
  20. Difference between timestamps with/without time zone in PostgreSQL
  21. Omitting the double quote to do query on PostgreSQL
  22. Storing Images in PostgreSQL
  23. Psql could not connect to server: No such file or directory, 5432 error?
  24. Strange behaviour in Postgresql
  25. Postgres: Distinct but only for one column
  26. Cursor based records in PostgreSQL
  27. How to add column if not exists on PostgreSQL?
  28. Maximum characters in labels (table names, columns etc)
  29. Docker – Postgres and pgAdmin 4 : Connection refused
  30. Configuration parameter work_mem in PostgreSQL on Linux

Leave a Comment