aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeMemoize.c
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2024-03-11 09:08:05 +0900
committerMichael Paquier <michael@paquier.xyz>2024-03-11 09:08:05 +0900
commitf500ba07fa9d00eaa2d26ea66401e62f950163ae (patch)
tree90b1d980c0f90b6a67c0061ee160e668c5a8960b /src/backend/executor/nodeMemoize.c
parenta04ddd077e61096da660e1c2f205e0c8277f2dcd (diff)
downloadpostgresql-f500ba07fa9d00eaa2d26ea66401e62f950163ae.tar.gz
postgresql-f500ba07fa9d00eaa2d26ea66401e62f950163ae.zip
Add some checkpoint and redo LSNs to a couple of recovery errors
Two FATALs and one PANIC gain details about the LSNs they fail at: - When restoring from a backup_label, the FATAL log generated when not finding the checkpoint record now reports its LSN. - When restoring from a backup_label, the FATAL log generated when not finding the redo record referenced by a checkpoint record now shows both the redo and checkpoint record LSNs. - When not restoring from a backup_label, the PANIC error generated when not finding the checkpoint record now reports its LSN. This information is useful when debugging corruption issues, and these LSNs may not show up in the logs depending on the level of logging configured in the backend. Author: David Steele Discussion: https://postgr.es/m/0e90da89-77ca-4ccf-872c-9626d755e288@pgmasters.net
Diffstat (limited to 'src/backend/executor/nodeMemoize.c')
0 files changed, 0 insertions, 0 deletions