my-ship-it commented on issue #1642: URL: https://github.com/apache/cloudberry/issues/1642#issuecomment-4140265252
Hi @adnanhamdussalam, Thanks for reporting this issue and providing the detailed logs — they're really helpful for diagnosing the problem! I took a look and compared the internal version identifiers (CATALOG_VERSION_NO, PG_CONTROL_VERSION, XLOG_PAGE_MAGIC, GP schema version) between 2.0.0 and 2.1.0. Good news: they are all **identical**, which means an in-place binary upgrade between these two versions should work just fine in general. So the issue you're seeing is most likely not caused by version incompatibility. Looking at the logs more closely, this line stands out: ``` database system was interrupted; last known up at 2026-03-25 13:50:32 EDT ``` This tells us the old 2.0.0 cluster wasn't cleanly shut down before the binary swap. Because of that, the database needs to perform WAL replay (crash recovery) to get back to a consistent state — but the checkpoint record it's looking for appears to be incomplete or invalid. **Here's what I'd recommend to recover:** 1. Restore the original 2.0.0 binaries. 2. Start the cluster with `gpstart -a` to let it perform crash recovery with the matching binaries. 3. Once it's up and running, do a clean shutdown: `gpstop -a -M fast`. 4. Now you can safely swap in the 2.1.0 binaries and start the cluster again. If step 2 also fails (meaning even the old binaries can't recover), the WAL/checkpoint data may have been affected by the interrupted startup attempt with the new binary. In that case, `pg_resetwal` could be used as a last resort, or you may need to restore from a backup. Feel free to follow up if you run into any other issues along the way — happy to help! 😊 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
