Re: Keepalive + pg_service.conf

Поиск
Список
Период
Сортировка
От Murtuza Zabuawala
Тема Re: Keepalive + pg_service.conf
Дата
Msg-id CAKKotZQErXXjiuwAvg3dDpH9BJdd9XtiZ-etZ42+AXjyVpbRBg@mail.gmail.com
обсуждение исходный текст
Ответ на Keepalive + pg_service.conf  (Durumdara <durumdara@gmail.com>)
Список pgadmin-support
Hi,

First, you have to create a Connection Service file 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@gmail.com> wrote:
Dear Developers!

I made report about a feature:

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

В списке pgadmin-support по дате отправления:

Предыдущее
От: Durumdara
Дата:
Сообщение: Keepalive + pg_service.conf
Следующее
От: Murtuza Zabuawala
Дата:
Сообщение: Re: v4 3.0 connection issues, notices is readonly