Re: [COMMITTERS] pgsql: Add GUC variables to control keep-alive

Поиск
Список
Период
Сортировка
От Oliver Jowett
Тема Re: [COMMITTERS] pgsql: Add GUC variables to control keep-alive
Дата
Msg-id 42EC1E54.5040808@opencloud.com
обсуждение исходный текст
Ответ на Re: [COMMITTERS] pgsql: Add GUC variables to control keep-alive  ("Larry Rosenman" <ler@lerctr.org>)
Ответы Re: [COMMITTERS] pgsql: Add GUC variables to control keep-alive  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
Larry Rosenman wrote:

> I think Tom's fix to use IPPROTO_TCP will fix firefly.

Ah, I forgot about the "we'll just use IP protocol numbers as socket
option levels" behaviour (BSD-derived?). My Linux man page only talks
about SOL_TCP, but I have run into this before and should have
remembered.. my bad.

per my linux/socket.h:

> /* Setsockoptions(2) level. Thanks to BSD these must match IPPROTO_xxx */
> #define SOL_IP          0
> /* #define SOL_ICMP     1       No-no-no! Due to Linux :-) we cannot use SOL_ICMP=1 */
> #define SOL_TCP         6

(I won't get into why using wire-level-protocol constants for syscall
option numbering is a bad idea.. :)

-O


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

Предыдущее
От: David Fetter
Дата:
Сообщение: Re: PL/Perl list value return causes segfault
Следующее
От: "Denis Lussier"
Дата:
Сообщение: Re: MySQL to PostgreSQL for SugarCRM