Skip site navigation (1) Skip section navigation (2)

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

From: Oliver Jowett <oliver(at)opencloud(dot)com>
To: Larry Rosenman <ler(at)lerctr(dot)org>
Cc: 'Andrew Dunstan' <andrew(at)dunslane(dot)net>,'Bruce Momjian' <pgman(at)candle(dot)pha(dot)pa(dot)us>,'Rocco Altier' <RoccoA(at)Routescape(dot)com>,'PostgreSQL-development' <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [COMMITTERS] pgsql: Add GUC variables to control keep-alive
Date: 2005-07-31 00:41:56
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-committerspgsql-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.. :)


In response to


pgsql-hackers by date

Next:From: Sergio A. KesslerDate: 2005-07-31 01:05:52
Subject: Re: MySQL to PostgreSQL for SugarCRM
Previous:From: David FetterDate: 2005-07-31 00:34:58
Subject: Re: [HACKERS] PL/Perl list value return causes segfault

pgsql-committers by date

Next:From: Larry RosenmanDate: 2005-07-31 02:53:01
Subject: Re: [COMMITTERS] pgsql: Add GUC variables to control keep-alive
Previous:From: User AndrewdDate: 2005-07-31 00:17:45
Subject: pgbuildfarm - client-code: feature code for the run-from-source

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group