Re: pg_dump, gzwrite, and errno - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: pg_dump, gzwrite, and errno
Date
Msg-id 20200619213047.GA7048@alvherre.pgsql
Whole thread Raw
In response to Re: pg_dump, gzwrite, and errno  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 2020-Jun-18, Tom Lane wrote:

> Surely it's insufficient as-is, because there is no reason to suppose
> that errno is zero at entry.  You'd need to set errno = 0 first.

Oh, right.

> Also it's fairly customary in our sources to include a comment about
> this machination; so the full ritual is usually more like

Yeah, I had that in my local copy.  Done like that in all the most
obvious places.  But there are more places that are still wrong: I
believe every single place that calls WRITE_ERROR_EXIT is doing the
wrong thing.

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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: More tzdb fun: POSIXRULES is being deprecated upstream
Next
From: Thomas Munro
Date:
Subject: Re: pg_regress cleans up tablespace twice.