Re: Call perror on popen failure

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>, Pgsql Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Call perror on popen failure
Date: 2024-03-08 17:08:38
Message-ID: 1fcfa6c1-7d8c-4e17-b0ce-848164c9f31d@eisentraut.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2024-03-08 17:09:12 Re: Remove unnecessary code from psql's watch command
Previous Message Melanie Plageman 2024-03-08 16:41:59 Re: Confine vacuum skip logic to lazy_scan_skip