Re: [HACKERS] [patch] pg_dump/pg_restore zerror() and strerror()mishap - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: [HACKERS] [patch] pg_dump/pg_restore zerror() and strerror()mishap
Date
Msg-id 20170622154004.e6bcw6juk2pwhngb@alvherre.pgsql
Whole thread Raw
In response to [HACKERS] [patch] pg_dump/pg_restore zerror() and strerror() mishap  (Kunshchikov Vladimir <Vladimir.Kunshchikov@infotecs.ru>)
List pgsql-hackers
Kunshchikov Vladimir wrote:

Hi,

>     our testing team has noticed apparently wrong backup/restore error messages like this:
> 
> 
> pg_restore: [compress_io] could not read from input file: success
> pg_dump: [directory archiver] could not write to output file: success
> 
> 
> 
> Such "success" messages are caused by calling strerror() after gzread()/gzwrite() failures.

Yeah, I've complained about this before but never got around to actually
fixing it.  Thanks for the patch, I'll see about putting it on all
branches soon.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: [HACKERS] Challenges preventing us moving to 64 bit transactionid (XID)?
Next
From: Alvaro Herrera
Date:
Subject: Re: [HACKERS] GSoC 2017 Proposal for predicate locking in hash index