Re: [GENERAL] Surviving connections after internet problem

Durumdara wrote: >> You can use pg_terminate_backend to kill a database session. >> >> Setting the keepalive options in postgresql.conf can make PostgreSQL >> discover dead connections more quickly. > > The server is licenced, so we can't access the conf file now. > We will report this to the

Re: [GENERAL] Surviving connections after internet problem

Dear Laurenz! 2016-11-07 16:06 GMT+01:00 Albe Laurenz : > Durumdara wrote: > > Linux server, 9.4 PG, Windows clients far-far away. > > May we must limit these parameters in clients after the starting of the > connection? > > Don't bother about the clients, just see that

Re: [GENERAL] Surviving connections after internet problem

Durumdara wrote: > 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

[GENERAL] Surviving connections after internet problem

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