Ensure write failure reports no-disk-space
authorAlvaro Herrera <alvherre@alvh.no-ip.org>
Fri, 19 Jun 2020 20:46:07 +0000 (16:46 -0400)
committerAlvaro Herrera <alvherre@alvh.no-ip.org>
Fri, 19 Jun 2020 20:46:07 +0000 (16:46 -0400)
commitae3259c55067c926d25c745d70265fca15c2d26b
tree0654198733c62ea551b4f8e6cac0c4f7125c2975
parent2c8ef9363db199aed9e8f17edba866b1215803c6
Ensure write failure reports no-disk-space

A few places calling fwrite and gzwrite were not setting errno to ENOSPC
when reporting errors, as is customary; this led to some failures being
reported as
"could not write file: Success"
which makes us look silly.  Make a few of these places in pg_dump and
pg_basebackup use our customary pattern.

Backpatch-to: 9.5
Author: Justin Pryzby <pryzby@telsasoft.com>
Author: Tom Lane <tgl@sss.pgh.pa.us>
Author: Álvaro Herrera <alvherre@alvh.no-ip.org>
Discussion: https://postgr.es/m/20200611153753.GU14879@telsasoft.com
src/bin/pg_basebackup/pg_basebackup.c
src/bin/pg_dump/pg_backup_directory.c