Re: Postgres keep alive configuration

From: Fabrice Chapuis <fabrice636861(at)gmail(dot)com>
To: "Daniel Westermann (DWE)" <daniel(dot)westermann(at)dbi-services(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Postgres keep alive configuration
Date: 2025-07-23 12:40:04
Message-ID: CAA5-nLD21fQ2SbSfyEFapH_TWpJ4w_WArHD8-wWcquMsho244Q@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: 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)

On Wed, Jul 23, 2025 at 1:30 PM Daniel Westermann (DWE) <
daniel(dot)westermann(at)dbi-services(dot)com> wrote:

> >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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Frédéric Yhuel 2025-07-23 12:45:10 Re: vacuumdb changes for stats import/export
Previous Message Srinath Reddy Sadipiralla 2025-07-23 12:40:00 is there any specific use of setting transaction_read_only GUC externally?