pgsql: Ensure write failure reports no-disk-space

2020-06-19 Thread Alvaro Herrera
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

pgsql: Ensure write failure reports no-disk-space

2020-06-19 Thread Alvaro Herrera
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

pgsql: Ensure write failure reports no-disk-space

2020-06-19 Thread Alvaro Herrera
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

pgsql: Ensure write failure reports no-disk-space

2020-06-19 Thread Alvaro Herrera
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

pgsql: Ensure write failure reports no-disk-space

2020-06-19 Thread Alvaro Herrera
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

pgsql: Ensure write failure reports no-disk-space

2020-06-19 Thread Alvaro Herrera
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

pgsql: Ensure write failure reports no-disk-space

2020-06-19 Thread Alvaro Herrera
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