From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Rob Sargent <robjsargent(at)gmail(dot)com> |
Cc: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: tcp settings |
Date: | 2022-09-20 23:21:43 |
Message-ID: | 934612.1663716103@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Rob Sargent <robjsargent(at)gmail(dot)com> writes:
> I'm wondering if there's a disconnect between my servers postgresql.conf
> and the system tcp settings? Are the config names supposed to match a
> file in /proc/sys/net/ipv4?
Probably not --- we certainly didn't pick them with the intention
of matching any specific system's naming of the options. On my
Linux box it looks like the related files are named
/proc/sys/net/ipv4/tcp_keepalive_XXX
But in any case, if this is your problem:
> My issue is that psql is timing out with "SSL SYSCALL error: Connection
> timed out".
then keepalives aren't necessarily the solution anyway. When is
this failure occurring ... is it while trying to establish the
database connection in the first place? Or does it only happen
if you've left the psql session sit idle for a long while?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Rob Sargent | 2022-09-21 00:46:15 | Re: tcp settings |
Previous Message | Theodore M Rolle, Jr. | 2022-09-20 22:54:29 | Re: I slipped up so that no existing role allows connection. Is rescue possible? |