Re: Postgres tcp_keepalive_xxxx parameters. - Mailing list pgsql-general

From Tom Lane
Subject Re: Postgres tcp_keepalive_xxxx parameters.
Date
Msg-id 10398.1412175846@sss.pgh.pa.us
Whole thread Raw
In response to Postgres tcp_keepalive_xxxx parameters.  (jlrando <jose.luis.rando.calvo@ericsson.com>)
Responses Re: Postgres tcp_keepalive_xxxx parameters.  (José Luis Rando Calvo<jose.luis.rando.calvo@ericsson.com>)
List pgsql-general
jlrando <jose.luis.rando.calvo@ericsson.com> writes:
> We have an issue with postgres clients tha are being disconnected from
> database server after some time. Client is a web application which creates a
> pool of connections. Since client and server are on different VLANS I think
> the problem is that the FW which is routing traffic is droping idle
> connections after some time.

Probably.  It might be asymmetric; have you tried enabling keepalives
from the client end, rather than the server?  If using libpq, you can
set keepalive parameters in the connection string:
http://www.postgresql.org/docs/9.3/static/libpq-connect.html#LIBPQ-PARAMKEYWORDS

If that doesn't fix it, you might want to get out Wireshark or a similar
tool and verify that keepalive packets are actually getting sent.

            regards, tom lane


pgsql-general by date:

Previous
From: Daniel Begin
Date:
Subject: Re: Best practices for Large import in empty database?
Next
From: Adam Brusselback
Date:
Subject: Re: table versioning approach (not auditing)