aboutsummaryrefslogtreecommitdiff
path: root/src/bin/pg_basebackup/walmethods.c
diff options
context:
space:
mode:
authorPeter Eisentraut <peter@eisentraut.org>2019-07-29 07:41:06 +0200
committerPeter Eisentraut <peter@eisentraut.org>2019-07-29 07:54:57 +0200
commit1e2fddfa33d3c7cc93ca3ee0f32852699bd3e012 (patch)
treef7b7e5d49b9baf01a57b3be42c030b74bffa3fb2 /src/bin/pg_basebackup/walmethods.c
parenteb43f3d19324d7e5376b1f57fc2e5c142a6b5f3d (diff)
downloadpostgresql-1e2fddfa33d3c7cc93ca3ee0f32852699bd3e012.tar.gz
postgresql-1e2fddfa33d3c7cc93ca3ee0f32852699bd3e012.zip
Handle fsync failures in pg_receivewal and pg_recvlogical
It is not safe to simply report an fsync error and continue. We must exit the program instead. Reviewed-by: Michael Paquier <michael@paquier.xyz> Reviewed-by: Sehrope Sarkuni <sehrope@jackdb.com> Discussion: https://www.postgresql.org/message-id/flat/9b49fe44-8f3e-eca9-5914-29e9e99030bf@2ndquadrant.com
Diffstat (limited to 'src/bin/pg_basebackup/walmethods.c')
-rw-r--r--src/bin/pg_basebackup/walmethods.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/bin/pg_basebackup/walmethods.c b/src/bin/pg_basebackup/walmethods.c
index 83b520898be..8ec12e6f723 100644
--- a/src/bin/pg_basebackup/walmethods.c
+++ b/src/bin/pg_basebackup/walmethods.c
@@ -864,7 +864,7 @@ tar_close(Walfile f, WalCloseMethod method)
/* Always fsync on close, so the padding gets fsynced */
if (tar_sync(f) < 0)
- return -1;
+ exit(1);
/* Clean up and done */
pg_free(tf->pathname);