MIME-Version: 1.0
References: 
 <CALFNBwepVWW6esjue4Eu9_EJ2tnA7KiSzt0ftAiivXiRGj87JQ@mail.gmail.com>
 <3477789.1699111986@sss.pgh.pa.us>
In-Reply-To: <3477789.1699111986@sss.pgh.pa.us>
From: =?UTF-8?B?7J207IOB7JuQ?= <swlee.kioplo@gmail.com>
Date: Mon, 6 Nov 2023 09:45:00 +0900
Message-ID: 
 <CALFNBwc86ueiFq528jmeEMNkK0mearWMB3NaaY_5PdYWSxdpmQ@mail.gmail.com>
Subject: Re: Connection Timeout Issue due to intermittent non-response of
 Postgre database
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-jdbc@lists.postgresql.org
Content-Type: multipart/alternative; boundary="000000000000b465a60609712aec"
Archived-At: 
 <https://www.postgresql.org/message-id/CALFNBwc86ueiFq528jmeEMNkK0mearWMB3NaaY_5PdYWSxdpmQ%40mail.gmail.com>
Precedence: bulk

--000000000000b465a60609712aec
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Thanks, I'll check it out. then, I will update to all.

2023=EB=85=84 11=EC=9B=94 5=EC=9D=BC (=EC=9D=BC) =EC=98=A4=EC=A0=84 12:33, =
Tom Lane <tgl@sss.pgh.pa.us>=EB=8B=98=EC=9D=B4 =EC=9E=91=EC=84=B1:

> =3D?UTF-8?B?7J207IOB7JuQ?=3D <swlee.kioplo@gmail.com> writes:
> > The Postgre database does not respond intermittently, causing a
> connection
> > timeout in the Spring Framework. There is no regularity in the occurren=
ce
> > of connection timeouts and they do not repeat continuously. Not easy to
> > track.
>
> I'd try turning on statement logging, and maybe also statement duration
> logging, and then matching up the times of observed client-side outages
> with what's happening according to the postmaster log.  Connection
> and disconnection logging might be useful too.
>
> A likely bet about the root cause is an unreasonably short connection
> timeout in some network infrastructure between your client and the
> database server.  That would manifest as both sides reporting that the
> other side disconnected (not necessarily at the same time, but for the
> same connection).  If so, it could likely be cured by adjusting the
> database's TCP keepalive settings.  But you ought to gather data
> first.
>
>                         regards, tom lane
>

--000000000000b465a60609712aec
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thanks, I&#39;ll check it out. then, I will update to all.=
<br></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_at=
tr">2023=EB=85=84 11=EC=9B=94 5=EC=9D=BC (=EC=9D=BC) =EC=98=A4=EC=A0=84 12:=
33, Tom Lane &lt;<a href=3D"mailto:tgl@sss.pgh.pa.us">tgl@sss.pgh.pa.us</a>=
&gt;=EB=8B=98=EC=9D=B4 =EC=9E=91=EC=84=B1:<br></div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,=
204,204);padding-left:1ex">=3D?UTF-8?B?7J207IOB7JuQ?=3D &lt;<a href=3D"mail=
to:swlee.kioplo@gmail.com" target=3D"_blank">swlee.kioplo@gmail.com</a>&gt;=
 writes:<br>
&gt; The Postgre database does not respond intermittently, causing a connec=
tion<br>
&gt; timeout in the Spring Framework. There is no regularity in the occurre=
nce<br>
&gt; of connection timeouts and they do not repeat continuously. Not easy t=
o<br>
&gt; track.<br>
<br>
I&#39;d try turning on statement logging, and maybe also statement duration=
<br>
logging, and then matching up the times of observed client-side outages<br>
with what&#39;s happening according to the postmaster log.=C2=A0 Connection=
<br>
and disconnection logging might be useful too.<br>
<br>
A likely bet about the root cause is an unreasonably short connection<br>
timeout in some network infrastructure between your client and the<br>
database server.=C2=A0 That would manifest as both sides reporting that the=
<br>
other side disconnected (not necessarily at the same time, but for the<br>
same connection).=C2=A0 If so, it could likely be cured by adjusting the<br=
>
database&#39;s TCP keepalive settings.=C2=A0 But you ought to gather data<b=
r>
first.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 regards, tom lane<br>
</blockquote></div>

--000000000000b465a60609712aec--