Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!nuzba.szn.dk!pnx.dk!fu-berlin.de!uni-berlin.de!not-for-mail From: "M. Strobel" Newsgroups: comp.databases.postgresql Subject: Re: Preventing a timeout on a connection Date: Thu, 28 Feb 2013 11:03:17 +0100 Lines: 25 Message-ID: References: <6f9ui8pi4ub903fl62kgg4t6793c5ph7b7@4ax.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Trace: news.uni-berlin.de ufLjd5LKz1GRtDfWcMdhHQt2UaY35ziM4/0Tx4qKRGocfbrc/Am4K2nvaxG57dMpU= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 In-Reply-To: <6f9ui8pi4ub903fl62kgg4t6793c5ph7b7@4ax.com> Xref: csiph.com comp.databases.postgresql:440 Am 28.02.2013 10:41, schrieb gargoyle60: > 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. I am following a different strategy, you might consider it: I do a timeout myself and close the connection on inactivity, the app sitting there on the desktop idle during lunch. Every use of the connection handle is encapsulated in a proc checking if it is connected, and connecting if not. I think this is a robust approach that might help as well with unstable network connections. /Str.