Re: Keepalive + pg_service.conf

Hi,

First, you have to create a Connection Service file
<https://www.postgresql.org/docs/9.1/static/libpq-pgservice.html> with
required connection parameters then you have to provide that service name
in server dialog.
Disconnect and re-connect the server.

Example: ~/.pg_service.conf

[mydb]keepalives=1
connect_timeout=20
keepalives_idle=10

Provide `*mydb`* value in the Service field in the Server dialog.

--
Regards,
Murtuza Zabuawala
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

On Mon, Apr 23, 2018 at 6:55 PM, Durumdara <durumdara(at)gmail(dot)com> wrote:

> Dear Developers!
>
> I made report about a feature:
> https://redmine.postgresql.org/issues/3120#change-11409
>
> You wrote this integrated with "pg_service.conf".
>
> How can I activate this?
>
> 1.) I set server "service" to "BLAH".
> 2.) I make a started batch file (as I did it with pgAdmin III):
> set PGSERVICEFILE=t:\pgadmin3_service.ini
> cd "c:\Program Files (x86)\pgAdmin 4\v3\runtime"
> "c:\Program Files (x86)\pgAdmin 4\v3\runtime\pgAdmin4.exe"
> 3.) I start PGA4 with this batch.
>
> And then?
>
> I want say that in PgAdmin III this "service" mode solved the timeouts,
> but the visual elements are changed, which caused more problems.
>
> We have more multidatabase servers.
> When I used PGA3 with service file, the service name used in every place
> when I saw database names formerly.
> So I lost in navigation, because I must checked the opened database name
> to be sure that Query tool is in the DB what I needed.
>
> I hope the PGA4 solution is better, it's not hide the database name (or
> replace with the service name).
> Connection parameters are in server level, not in database.
>
> Thank you for the help!
>
> dd
>