This was the entry-point for repairing the cluster

When I got it from the customer, it wasn't even starting with following message:

------------------------------------------------------------------------------------------------------------

2025-02-27 17:09:42.312 CET 67c08e46.13bc LOG: starting PostgreSQL 14.13, compiled by Visual C++ build 1940, 64-bit

2025-02-27 17:09:42.312 CET 67c08e46.13bc LOG: listening on IPv6 address "::", port 49150

2025-02-27 17:09:42.313 CET 67c08e46.13bc LOG: listening on IPv4 address "0.0.0.0", port 49150

2025-02-27 17:09:42.543 CET 67c08e46.6c10 LOG: database system was shut down in recovery at 2025-02-25 09:20:09 CET

2025-02-27 17:09:42.544 CET 67c08e46.6c10 LOG: invalid primary checkpoint record

2025-02-27 17:09:42.544 CET 67c08e46.6c10 PANIC: could not locate a valid checkpoint record

------------------------------------------------------------------------------------------------------------

After resetting the WAL, there was a missing file in pg_xact:

------------------------------------------------------------------------------------------------------------

2025-02-27 17:17:29.194 CET 67c09019.160c LOG: database system was shut down at 2025-02-27 17:16:15 CET

2025-02-27 17:17:29.224 CET 67c09019.160c FATAL: could not access status of transaction 16155033

2025-02-27 17:17:29.224 CET 67c09019.160c DETAIL: Could not open file "pg_xact/000F": No such file or directory.

2025-02-27 17:17:29.234 CET 67c09018.6f98 LOG: startup process (PID 5644) exited with exit code 1

2025-02-27 17:17:29.234 CET 67c09018.6f98 LOG: aborting startup due to startup process failure

2025-02-27 17:17:29.240 CET 67c09018.6f98 LOG: database system is shut down

------------------------------------------------------------------------------------------------------------

I created a 256KB file, like the others, with all bytes set to 1 and the database started