Re: Call perror on popen failure - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Call perror on popen failure
Date
Msg-id 1fcfa6c1-7d8c-4e17-b0ce-848164c9f31d@eisentraut.org
Whole thread Raw
In response to Call perror on popen failure  (Daniel Gustafsson <daniel@yesql.se>)
Responses Re: Call perror on popen failure
List pgsql-hackers
On 08.03.24 11:05, Daniel Gustafsson wrote:
> If popen fails in pipe_read_line we invoke perror for the error message, and
> pipe_read_line is in turn called by find_other_exec which is used in both
> frontend and backend code.  This is an old codepath, and it seems like it ought
> to be replaced with the more common logging tools we now have like in the
> attached diff (which also makes the error translated as opposed to now).  Any
> objections to removing this last perror() call?

This change makes it consistent with other popen() calls, so it makes 
sense to me.




pgsql-hackers by date:

Previous
From: Melanie Plageman
Date:
Subject: Re: Confine vacuum skip logic to lazy_scan_skip
Next
From: Tom Lane
Date:
Subject: Re: Remove unnecessary code from psql's watch command