Re: Postgres keep alive configuration
| От | Fabrice Chapuis |
|---|---|
| Тема | Re: Postgres keep alive configuration |
| Дата | |
| Msg-id | CAA5-nLD21fQ2SbSfyEFapH_TWpJ4w_WArHD8-wWcquMsho244Q@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Postgres keep alive configuration ("Daniel Westermann (DWE)" <daniel.westermann@dbi-services.com>) |
| Список | pgsql-hackers |
Ok Thanks Daniel
It show the right value with the connection over the network
Regards
Fabrice
postgres [2867156]=> show tcp_keepalives_idle;
+---------------------+
| tcp_keepalives_idle |
+---------------------+
| 3 |
+---------------------+
(1 row)
+---------------------+
| tcp_keepalives_idle |
+---------------------+
| 3 |
+---------------------+
(1 row)
On Wed, Jul 23, 2025 at 1:30 PM Daniel Westermann (DWE) <daniel.westermann@dbi-services.com> wrote:
>From: Fabrice Chapuis <fabrice636861@gmail.com>
>Sent: Wednesday, July 23, 2025 13:20
>To: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
>Subject: Postgres keep alive configuration
>
>Hi,
>
>I try to configure these 3 parameters to activate keep alive on a sever Postgres in version 14.
>
>tcp_keepalives_idle = 3
>tcp_keepalives_interval = 2
>tcp_keepalives_count = 30
>After issuing alter system set ... command and a pg_reload_conf(); these parameters keep value 0.
Did you create a connection over the network when checking the values or are you connected over a socket? For socket connections these values will always be 0.
Regards
Daniel
В списке pgsql-hackers по дате отправления: