[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gnumed-devel] client tcp/ip and Postgres timeouts (was encounter edit b

From: James Busser
Subject: [Gnumed-devel] client tcp/ip and Postgres timeouts (was encounter edit before final save)
Date: Fri, 15 Aug 2008 21:02:12 -0700

On 15-Aug-08, at 5:06 AM, Karsten Hilbert wrote:

Is there however a
caveat with respect to a "timeout" after which the database will not
allow the paused instance to write into the backend?
There is, at the purely technical level.

Where and how would this configuration be set?
The TCP/IP stack timeout is one place I can think of.

Is the above (the TCP/IP stack timeout setting) managed at a system level on both the client computer and on the server? ... looks like a default may be 60 seconds but maybe something else would keep the client connection alive?

Are connection timeout limits further managed within PostgreSQL or only if we configure them to be so?

        ... postgres evidently includes some "persistence" configurations
        ... however are we decided to avoid or limit persistence?

If the above is correct, then the timeout would in practice be determined by whichever is the shortest of the above?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]