I think your log shows a continued archive recovery (PITR), not a crash
recovery.
For a crash recovery (automatic recovery), you would see something like
this in the server log:
LOG: database system was interrupted; last known up at 2022-12-23
20:50:13 CET
LOG: database system was not pro
We are using Crunchy PGO which uses "pgbackrest".
Over Christmas we had a disk full error on the "pgbackrest" repo followed by a
disk full error on the PostgreSQL instance pod.
Unfortunately, a colleague then deleted the current "pg_wal" directory on the
instance pod.
So we had to do a point-in-t
