Re: Fix handling of invalid sockets returned by PQsocket()

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема Re: Fix handling of invalid sockets returned by PQsocket()
Дата
Msg-id 56DB6C5A.5050205@gmx.net
обсуждение исходный текст
Ответ на Re: Fix handling of invalid sockets returned by PQsocket()  (Michael Paquier <michael.paquier@gmail.com>)
Ответы Re: Fix handling of invalid sockets returned by PQsocket()
Список pgsql-hackers
On 2/17/16 10:52 PM, Michael Paquier wrote:
> On Thu, Feb 18, 2016 at 1:58 AM, Alvaro Herrera
> <alvherre@2ndquadrant.com> wrote:
>> Michael Paquier wrote:
>>> Hi all,
>>>
>>> After looking at Alvaro's message mentioning the handling of
>>> PQsocket() for invalid sockets, I just had a look by curiosity at
>>> other calls of this routine, and found a couple of issues:
>>> 1) In vacuumdb.c, init_slot() does not check for the return value of PQsocket():
>>> slot->sock = PQsocket(conn);
>>> 2) In isolationtester.c, try_complete_step() should do the same.
>>> 3) In pg_recvlogical.c for StreamLogicalLog() I am spotting the same problem.
>>> I guess those ones should be fixed as well, no?
>>
>> I patched pgbench to use PQerrorMessage rather than strerror(errno).  I
>> think your patch should do the same.
> 
> OK, this looks like a good idea. I would suggest doing the same in
> receivelog.c then.

Let's make the error messages consistent as "invalid socket".  "bad
socket" isn't really our style, and pg_basebackup saying "socket not
open" is just plain incorrect.




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

Предыдущее
От: Andrew Dunstan
Дата:
Сообщение: Re: VS 2015 support in src/tools/msvc
Следующее
От: David Rowley
Дата:
Сообщение: Re: Performance improvement for joins where outer side is unique