| From: | "Daniel Westermann (DWE)" <daniel(dot)westermann(at)dbi-services(dot)com> |
|---|---|
| To: | Fabrice Chapuis <fabrice636861(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Postgres keep alive configuration |
| Date: | 2025-07-23 11:30:54 |
| Message-ID: | ZRZP278MB18414E210E7E17A4E7FBD270D25FA@ZRZP278MB1841.CHEP278.PROD.OUTLOOK.COM |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>From: Fabrice Chapuis <fabrice636861(at)gmail(dot)com>
>Sent: Wednesday, July 23, 2025 13:20
>To: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Verite | 2025-07-23 11:53:52 | Re: Collation and primary keys |
| Previous Message | Fabrice Chapuis | 2025-07-23 11:20:52 | Postgres keep alive configuration |