Re: Surviving connections after internet problem

From: Durumdara <durumdara(at)gmail(dot)com>
To: Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>
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:32:05
Message-ID: CAEcMXhmEQZ-GTS2f_zP82sT+1kOD4P1ZVFtUC8KTXbk4uRm=kg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Dear Laurenz!

2016-11-07 16:06 GMT+01:00 Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>:

> 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 the backends go away on the
> server.
>
> 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.

For that moment could we set these parameters from clients after the
connection established?

For example:

set param bla = nnn?

Thank you!

Regards
dd

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Albe Laurenz 2016-11-08 10:37:03 Re: Linux equivalent library for "postgres.lib" from Windows
Previous Message Michael Paquier 2016-11-08 05:15:35 Re: Linux equivalent library for "postgres.lib" from Windows