Re: Call perror on popen failure

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Peter Eisentraut <peter(at)eisentraut(dot)org>
Cc: Pgsql Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Call perror on popen failure
Date: 2024-03-08 23:05:34
Message-ID: D8A5B58F-335D-49B3-BBD8-A6F507435B8A@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 8 Mar 2024, at 18:08, Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:
>
> 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.

Thanks for review, committed that way.

--
Daniel Gustafsson

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Gustafsson 2024-03-08 23:06:15 Re: pipe_read_line for reading arbitrary strings
Previous Message Thomas Munro 2024-03-08 22:24:15 Re: Streaming I/O, vectored I/O (WIP)