aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistget.c
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2023-10-30 15:28:20 +0900
committerMichael Paquier <michael@paquier.xyz>2023-10-30 15:28:20 +0900
commitdc5bd38894373e6806289e3aca26e7fafa5f6f95 (patch)
treed9df79391b20bd4ede3a9bf1cc00a21c222265e6 /src/backend/access/gist/gistget.c
parentc4ede4fdfb9c7c3480a8139ac706498ffcf35fb6 (diff)
downloadpostgresql-dc5bd38894373e6806289e3aca26e7fafa5f6f95.tar.gz
postgresql-dc5bd38894373e6806289e3aca26e7fafa5f6f95.zip
Delay recovery mode LOG after reading backup_label and/or checkpoint record
When beginning recovery, a LOG is displayed by the startup process to show which recovery mode will be used depending on the .signal file(s) set in the data folder, like "standby mode", recovery up to a given target type and value, or archive recovery. A different patch is under discussion to simplify the startup code by requiring the presence of recovery.signal and/or standby.signal when a backup_label file is read. Delaying a bit this LOG ensures that the correct recovery mode would be reported, and putting it at this position does not make it lose its value. While on it, this commit adds a few comments documenting a bit more the initial recovery steps and their dependencies, and fixes an incorrect comment format. This introduces no behavior changes. Extracted from a larger patch by me. Reviewed-by: David Steele, Bowen Shi Discussion: https://postgr.es/m/ZArVOMifjzE7f8W7@paquier.xyz
Diffstat (limited to 'src/backend/access/gist/gistget.c')
0 files changed, 0 insertions, 0 deletions