postgresql/src/bin/pg_basebackup
Peter Eisentraut 1e2fddfa33 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
2019-07-29 07:54:57 +02:00
..
po Translation updates 2019-06-17 15:30:20 +02:00
t Fix typos in various places 2019-06-03 13:44:03 +09:00
.gitignore Rename user-facing tools with "xlog" in the name to say "wal". 2017-02-09 16:23:46 -05:00
Makefile Update copyright for 2019 2019-01-02 12:44:25 -05:00
nls.mk Unified logging system for command-line programs 2019-04-01 20:01:35 +02:00
pg_basebackup.c Don't uselessly escape a string that doesn't need escaping 2019-07-26 17:46:40 -04:00
pg_receivewal.c Phase 2 pgindent run for v12. 2019-05-22 13:04:48 -04:00
pg_recvlogical.c Handle fsync failures in pg_receivewal and pg_recvlogical 2019-07-29 07:54:57 +02:00
receivelog.c Handle fsync failures in pg_receivewal and pg_recvlogical 2019-07-29 07:54:57 +02:00
receivelog.h Phase 2 pgindent run for v12. 2019-05-22 13:04:48 -04:00
streamutil.c Use appendStringInfoString and appendPQExpBufferStr where possible 2019-07-04 13:01:13 +12:00
streamutil.h Phase 2 pgindent run for v12. 2019-05-22 13:04:48 -04:00
walmethods.c Handle fsync failures in pg_receivewal and pg_recvlogical 2019-07-29 07:54:57 +02:00
walmethods.h Phase 2 pgindent run for v12. 2019-05-22 13:04:48 -04:00