From: | Durumdara <durumdara(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Surviving connections after internet problem |
Date: | 2016-11-07 13:12:13 |
Message-ID: | CAEcMXhk6WUGLLu=mSR+Bn9=6=kEAXhuj5eyMHvyKzGXuh2Ovcg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hello!
Linux server, 9.4 PG, Windows clients far-far away.
They called us that they had an "internet reset" at 13.00, but many client
locks are alive now (14:00).
I checked server status, and and saw 16 connections.
In Windows PG server I read about keepalive parameters which are control
and redefine default TCP keepalive values.
As I read it could be two hours in Windows, and it is a system default, so
we can change for all applications.
I don't know what happens with Linux server and Windows clients.
May Linux version of PGSQL also uses 2 hour keepalive (default), or the it
caused by Windows clients, or an active device?
Or how could they survive this internet connection reset? :-o
May we must limit these parameters in clients after the starting of the
connection?
Thank you for your help!
dd
From | Date | Subject | |
---|---|---|---|
Next Message | Albe Laurenz | 2016-11-07 13:12:43 | Re: Database Recovery from Corrupted Dump or Raw database table file. |
Previous Message | Howard News | 2016-11-07 12:44:51 | Database Recovery from Corrupted Dump or Raw database table file. |