aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistxlog.c
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2021-10-28 10:49:26 +0900
committerMichael Paquier <michael@paquier.xyz>2021-10-28 10:49:26 +0900
commit46dea2419ee7895a4eb3d048317682e6f18a17e1 (patch)
treeb46801d449287e06bf7338c56c10ae53a3f442f8 /src/backend/access/gist/gistxlog.c
parentcc1853b30048307d93f8aa30f4d64f88b527f04d (diff)
downloadpostgresql-46dea2419ee7895a4eb3d048317682e6f18a17e1.tar.gz
postgresql-46dea2419ee7895a4eb3d048317682e6f18a17e1.zip
Add TAP test for archive_cleanup_command and recovery_end_command
This adds tests checking for the execution of both commands. The recovery test 002_archiving.pl is nicely adapted to that, as promotion is triggered already twice there, and even if any of those commands fail they don't affect recovery or promotion. A command success is checked using a file generated by an "echo" command, that should be able to work in all the buildfarm environments, even Msys (but we'll know soon about that). Command failure is tested with an "echo" command that points to a path that does not exist, scanning the backend logs to make sure that the failure happens. Both rely on the backend triggering the commands from the root of the data folder, making its logic more robust. Thanks to Neha Sharma for the extra tests on Windows. Author: Amul Sul, Michael Paquier Reviewed-by: Andres Freund, Euler Taveira Discussion: https://postgr.es/m/CAAJ_b95R_c4T5moq30qsybSU=eDzDHm=4SPiAWaiMWc2OW7=1Q@mail.gmail.com
Diffstat (limited to 'src/backend/access/gist/gistxlog.c')
0 files changed, 0 insertions, 0 deletions