Fix FATAL message for invalid recovery timeline at beginning of recovery
authorMichael Paquier <michael@paquier.xyz>
Thu, 20 Feb 2025 01:42:20 +0000 (10:42 +0900)
committerMichael Paquier <michael@paquier.xyz>
Thu, 20 Feb 2025 01:42:20 +0000 (10:42 +0900)
commit71f17823ba010296da9946bd906bb8bcad6325bc
tree7cda658e6aaf37a50ff13549898ef54c177c5e59
parentd38bab5edd60dbe6309512b6c8daea37ce579b70
Fix FATAL message for invalid recovery timeline at beginning of recovery

If the requested recovery timeline is not reachable, the logged
checkpoint and timeline should to be the values read from the
backup_label when it is defined.  The message generated used the values
from the control file in this case, which is fine when recovering from
the control file without a backup_label, but not if there is a
backup_label.

Issue introduced in ee994272ca50.  v15 has introduced xlogrecovery.c and
more simplifications in this area (4a92a1c3d1c3a27048cbcb58), making
this change a bit simpler to think about, so backpatch only down to this
version.

Author: David Steele <david@pgbackrest.org>
Reviewed-by: Andrey M. Borodin <x4mmm@yandex-team.ru>
Reviewed-by: Benoit Lobréau <benoit.lobreau@dalibo.com>
Discussion: http://postgr.es/m/c3d617d4-1696-4aa7-8a4d-5a7d19cc5618@pgbackrest.org
Backpatch-through: 15
src/backend/access/transam/xlogrecovery.c