aboutsummaryrefslogtreecommitdiff
path: root/contrib/btree_gist/btree_gist.h
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2023-10-30 13:56:02 +0900
committerMichael Paquier <michael@paquier.xyz>2023-10-30 13:56:02 +0900
commit1ffdc03c21ae78981b93297ae977841b59793eb7 (patch)
tree4e8b5f8d90d72e600f17a5dcb3e44e5faefa6654 /contrib/btree_gist/btree_gist.h
parent96f052613f35d07d001c8dd2f284ca8d95f82d1b (diff)
downloadpostgresql-1ffdc03c21ae78981b93297ae977841b59793eb7.tar.gz
postgresql-1ffdc03c21ae78981b93297ae977841b59793eb7.zip
Mention standby.signal in FATALs for checkpoint record missing at recovery
When beginning recovery from a base backup by reading a backup_label file, it may be possible that no checkpoint record is available depending on the method used when the case backup was taken, which would prevent recovery from beginning. In this case, the FATAL messages issued, initially added by c900c15269f0f, mentioned recovery.signal as an option to do recovery but not standby.signal. Let's add it as an available option, for clarity. Per suggestion from Bowen Shi, extracted from a larger patch by me. Author: Michael Paquier Discussion: https://postgr.es/m/CAM_vCudkSjr7NsNKSdjwtfAm9dbzepY6beZ5DP177POKy8=2aw@mail.gmail.com
Diffstat (limited to 'contrib/btree_gist/btree_gist.h')
0 files changed, 0 insertions, 0 deletions