diff options
author | Michael Paquier <michael@paquier.xyz> | 2023-01-16 16:31:43 +0900 |
---|---|---|
committer | Michael Paquier <michael@paquier.xyz> | 2023-01-16 16:31:43 +0900 |
commit | 9a740f81eb02e04179d78f3df2ce671276c27b07 (patch) | |
tree | 74377420cb332855295542dcf1e21db126c0e251 /src/backend/access/gist/gistbuildbuffers.c | |
parent | 02d3448f4f792964995b8071fa07176606e1af85 (diff) | |
download | postgresql-9a740f81eb02e04179d78f3df2ce671276c27b07.tar.gz postgresql-9a740f81eb02e04179d78f3df2ce671276c27b07.zip |
Refactor code in charge of running shell-based recovery commands
The code specific to the execution of archive_cleanup_command,
recovery_end_command and restore_command is moved to a new file named
shell_restore.c. The code is split into three functions:
- shell_restore(), that attempts the execution of a shell-based
restore_command.
- shell_archive_cleanup(), for archive_cleanup_command.
- shell_recovery_end(), for recovery_end_command.
This introduces no functional changes, with failure patterns and logs
generated in consequence being the same as before (one case actually
generates one less DEBUG2 message "could not restore" when a restore
command succeeds but the follow-up stat() to check the size fails, but
that only matters with a elevel high enough).
This is preparatory work for allowing recovery modules, a facility
similar to archive modules, with callbacks shaped similarly to the
functions introduced here.
Author: Nathan Bossart
Reviewed-by: Andres Freund, Michael Paquier
Discussion: https://postgr.es/m/20221227192449.GA3672473@nathanxps13
Diffstat (limited to 'src/backend/access/gist/gistbuildbuffers.c')
0 files changed, 0 insertions, 0 deletions