Call perror on popen failure

Поиск
Список
Период
Сортировка
От Daniel Gustafsson
Тема Call perror on popen failure
Дата
Msg-id 89B00F63-40F7-4D82-8353-DC9CABBAC1D1@yesql.se
обсуждение исходный текст
Ответы Re: Call perror on popen failure  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Call perror on popen failure  (Peter Eisentraut <peter@eisentraut.org>)
Список pgsql-hackers
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?

--
Daniel Gustafsson


Вложения

В списке pgsql-hackers по дате отправления:

Предыдущее
От: "Andrey M. Borodin"
Дата:
Сообщение: Re: speed up a logical replica setup
Следующее
От: Bharath Rupireddy
Дата:
Сообщение: Re: Add new error_action COPY ON_ERROR "log"