Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.databases.postgresql > #441

Re: Preventing a timeout on a connection

From Jasen Betts <jasen@xnet.co.nz>
Newsgroups comp.databases.postgresql
Subject Re: Preventing a timeout on a connection
Date 2013-02-28 11:00 +0000
Organization Dis (not Dat) Organisation
Message-ID <kgndbu$ggb$2@gonzo.reversiblemaps.ath.cx> (permalink)
References <6f9ui8pi4ub903fl62kgg4t6793c5ph7b7@4ax.com>

Show all headers | View raw


On 2013-02-28, gargoyle60 <gargoyle60@example.invalid> wrote:
> In one of my background applications I keep getting a peer communication error stating that a
> timeout occurred on a connection.
>
> The program runs for most of the day processing background statistics. It has an open "connected"
> connection but not always an active session on that connection, which is why I believe that the
> timeout occurs because it is sitting idle. The timeout is not on a SQL statement or similar, but on
> the idle connection.
>
> Is there a specific parameter in one of the conf files or elsewhere that would help extend any
> idle/timeout period (I've looked in the documentation but haven't been able to find anything
> specific to connections alone).
>
> I am using postgres 9.0.4 on Windows XP Home SP3.
>
> Thanks

set some keepalives on the cnnection

 http://www.postgresql.org/docs/9.2/interactive/libpq-connect.html#LIBPQ-CONNSTRING

-- 
⚂⚃ 100% natural

--- news://freenews.netfront.net/ - complaints: news@netfront.net ---

Back to comp.databases.postgresql | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Preventing a timeout on a connection gargoyle60 <gargoyle60@example.invalid> - 2013-02-28 09:41 +0000
  Re: Preventing a timeout on a connection "M. Strobel" <sorry_no_mail_here@nowhere.dee> - 2013-02-28 11:03 +0100
  Re: Preventing a timeout on a connection Jasen Betts <jasen@xnet.co.nz> - 2013-02-28 11:00 +0000
  Re: Preventing a timeout on a connection gargoyle60 <gargoyle60@example.invalid> - 2013-03-01 13:16 +0000

csiph-web