When restoring WAL files in parallel, the code assumes they are 16MB, and calculates the names of the WALs to download in parallel.
If the WALs are not the default size, it is possible that some of these evaluated names do not exist. This happens if a backup spans across multiple segments. If the restore tries to restore one of these not existing WALs and fails, it will error with a end of WAL reached and Set end-of-wal-stream flag as one of the WAL files to be prefetched was not found. This stops WAL restore.
If the backup spans multiple segments, the backup will be inconsistent, as the next segment is required.
As a workaround, setting maxParallel to 1 works.
When restoring WAL files in parallel, the code assumes they are 16MB, and calculates the names of the WALs to download in parallel.
If the WALs are not the default size, it is possible that some of these evaluated names do not exist. This happens if a backup spans across multiple segments. If the restore tries to restore one of these not existing WALs and fails, it will error with a
end of WAL reachedandSet end-of-wal-stream flag as one of the WAL files to be prefetched was not found. This stops WAL restore.If the backup spans multiple segments, the backup will be inconsistent, as the next segment is required.
As a workaround, setting maxParallel to 1 works.