Here are 3 $POSGRES_HOME/data/postgresql.conf parameters which may help 
tcp_keepalives_idle (integer)        On systems that support the TCP_KEEPIDLE 
socket option, specifies the
        number of seconds between sending keepalives on an otherwise idle
        connection. A value of 0 uses the system default. If TCP_KEEPIDLE is
        not supported, this parameter must be 0. This option is ignored for
        connections made via a Unix-domain socket.
       
tcp_keepalives_interval (integer)        On systems that support the 
TCP_KEEPINTVL socket option, specifies how
        long, in seconds, to wait for a response to a keepalive before
        retransmitting. A value of 0 uses the system default. If TCP_KEEPINTVL
        is not supported, this parameter must be 0. This option is ignored
        for connections made via a Unix-domain socket.
       
tcp_keepalives_count (integer)        On systems that support the TCP_KEEPCNT 
socket option, specifies how
        many keepalives may be lost before the connection is considered dead. 
        A value of 0 uses the system default. If TCP_KEEPCNT is not
        supported, this parameter must be 0. This option is ignored
        for connections made via a Unix-domain socket.
       
if all 3 parameters are left at 0 then the OS is supplying the keepalive 
parameters
here are my keepalive parameters from $POSTGRES_HOME/data/postgresql.conf
# - TCP Keepalives -
# see 'man 7 tcp' for details

#tcp_keepalives_idle = 0        # TCP_KEEPIDLE, in seconds;
                    # 0 selects the system default
#tcp_keepalives_interval = 0        # TCP_KEEPINTVL, in seconds;
                    # 0 selects the system default
#tcp_keepalives_count = 0        # TCP_KEEPCNT;
                    # 0 selects the system default

does this help?
Martin Gainty 
______________________________________________ 
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
 Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger 
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung 
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem 
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. 
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung 
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le 
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez 
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est 
interdite. Ce message sert à l'information seulement et n'aura pas n'importe 
quel effet légalement obligatoire. Étant donné que les email peuvent facilement 
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité 
pour le contenu fourni.




> Subject: [GENERAL] Configure server firewall request/response
> Date: Fri, 29 May 2009 15:22:16 +0200
> From: lars.carls...@epsilon.nu
> To: pgsql-general@postgresql.org
> 
> 
> Hi
> I use a .net ODBC connection and the connection to Pgsql db is though a 
> firewall that only allow request and a answer to the response.
> 
> I some times get Error from the client
> 
> "The connection has been disabled. ---> System.Data.Odbc.OdbcException: ERROR 
> [08S01] No response from the backend;"
> 
> I check the firewall logs and it seems like some responses get blocked in the 
> firewall could this be slow response or some kind of keep alive response.
> Are there some settings to make the Pgsql db server to work better with a 
> firewall request/response the KeepAlive is turned off.
> 
> regards
> Lars 
> 
> -- 
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general

_________________________________________________________________
Hotmail® has a new way to see what's up with your friends.
http://windowslive.com/Tutorial/Hotmail/WhatsNew?ocid=TXT_TAGLM_WL_HM_Tutorial_WhatsNew1_052009

Reply via email to