Re: Surviving connections after internet problem

From: Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>
To: "'Durumdara *EXTERN*'" <durumdara(at)gmail(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Surviving connections after internet problem
Date: 2016-11-08 10:42:30
Message-ID: A737B7A37273E048B164557ADEF4A58B5397A9BA@ntex2010i.host.magwien.gv.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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 provider.

You cannot use ALTER SYSTEM from SQL either?

> For that moment could we set these parameters from clients after the connection established?
>
> For example:
>
> set param bla = nnn?

Yes, that should work, e.g.:

SET tcp_keepalives_idle = 600;

Yours,
Laurenz Albe

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2016-11-08 14:44:34 Re: Fwd: Creating multiple instances of postresql on Windows environment
Previous Message Albe Laurenz 2016-11-08 10:37:03 Re: Linux equivalent library for "postgres.lib" from Windows