Hi,
This parameter is supported only on systems that support TCP_KEEPINTVL. And
please ensure that you are not accidentally connecting through a
Unix-domain socket. If the result of this query is null then it is a Unix
socket based connection.
SELECT client_addr FROM pg_stat_activity WHERE pid =
"Abraham, Danny" writes:
> Change tcp_keepalives_idle in postgresql.conf from 0 to 300 , then pg_ctl
> reload but it stays with the old 0 value.
> Tried restart and it did not work. PG Log says it was changed.
tcp_keepalives_idle isn't implemented on all platforms. But I'd
expect to see a LOG m
On 8/4/24 04:16, Abraham, Danny wrote:
Hi,
Change tcp_keepalives_idle in postgresql.conf from 0 to 300 , then pg_ctl
reload but it stays with the old 0 value.
Tried restart and it did not work. PG Log says it was changed.
Reset_cal marked OK, but no real change ( ins how)
-[ RECORD 1 ]---+
Hi,
Change tcp_keepalives_idle in postgresql.conf from 0 to 300 , then pg_ctl
reload but it stays with the old 0 value.
Tried restart and it did not work. PG Log says it was changed.
Reset_cal marked OK, but no real change ( ins how)
-[ RECORD 1 ]---+-
