Improve FATAL message for invalid TLI history at recovery The original message did not mention where the checkpoint record LSN was found, a control file or a backup_label file. A couple of LOG messages are generated before this FATAL check is reached, providing more details about the way recovery is set up. However, knowing this information in this specific message is useful for debugging. This is also useful for instances where log_min_messages is set to FATAL or more, where LOG messages do not show up.
Author: Benoit Lobréau <benoit.lobr...@dalibo.com> Reviewed-by: David Steele <da...@pgbackrest.org> Discussion: https://postgr.es/m/4ed10bc8-5513-4d8e-8643-8abcaa083...@dalibo.com Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/adc6032fa8824e7653252b02abc6a59d8b9d01a6 Modified Files -------------- src/backend/access/transam/xlogrecovery.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
