MIME-Version: 1.0
References: 
 <CA+mi_8ZH-feQP0+k_j7_joygE=hMZCFnaNMv8Z1KCLKB9YLb0w@mail.gmail.com>
 <CAP50yQ_Mt=RtR0sXYoazJTuarphR1Kv8A6YTevCMiv+xZeD9=Q@mail.gmail.com>
In-Reply-To: 
 <CAP50yQ_Mt=RtR0sXYoazJTuarphR1Kv8A6YTevCMiv+xZeD9=Q@mail.gmail.com>
From: Daniele Varrazzo <daniele.varrazzo@gmail.com>
Date: Mon, 30 Mar 2020 22:17:53 +1300
Message-ID: 
 <CA+mi_8YUNBR7yE1MgmRPoL0E4JcrjRGR97gTCtOxzswRwJrPMg@mail.gmail.com>
Subject: Re: psycopg3: a first report
To: Stefan Knecht <knecht.stefan@gmail.com>
Cc: psycopg@postgresql.org
Content-Type: multipart/alternative; boundary="000000000000c4c63905a20eedde"
Precedence: bulk

--000000000000c4c63905a20eedde
Content-Type: text/plain; charset="UTF-8"

Hi Stefan,

On Mon, 30 Mar 2020, 17:27 Stefan Knecht, <knecht.stefan@gmail.com> wrote:

>
If I may, one thing that has been a constant troublemaker for us - running
> primarily on AWS - is timeouts. I would love to see a fundamental
> implementation of timeouts at the connection level, regardless of activity
> - e.g. in the middle of a query, between queries, etc.. If the connection
> hangs (because the server disappeared or failed over) or does not respond
> (particularly in the weird cases like when the destination IP just vanishes
> and the tcp timeout kicks in) - I'd like to know about it within a
> reasonable time and be able to react to that.
>

It would be interesting to set up integration tests wirh connections being
disrupted in various ways and at different moments during connection and
query processes. I'd rather do them in a test framework rather than one-off.

Mitmproxy could be a nice tool to build them.

https://mitmproxy.org/

-- Daniele

>

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

<div dir=3D"auto"><div>Hi Stefan,<br><br><div class=3D"gmail_quote"><div di=
r=3D"ltr" class=3D"gmail_attr">On Mon, 30 Mar 2020, 17:27 Stefan Knecht, &l=
t;<a href=3D"mailto:knecht.stefan@gmail.com">knecht.stefan@gmail.com</a>&gt=
; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div></di=
v><div></div></div></blockquote></div></div><div dir=3D"auto"><br></div><di=
v dir=3D"auto"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote"=
 style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><d=
iv dir=3D"ltr"><div>If I may, one thing that has been a constant troublemak=
er for us - running primarily on AWS - is timeouts. I would love to see a f=
undamental implementation of timeouts at the connection level, regardless o=
f activity - e.g. in the middle of a query, between queries, etc.. If the c=
onnection hangs (because the server disappeared or failed over) or does not=
 respond (particularly in the weird cases like when the destination IP just=
 vanishes and the tcp timeout kicks in) - I&#39;d like to know about it wit=
hin a reasonable time and be able to react to that.<br></div></div></blockq=
uote></div></div><div dir=3D"auto"><br></div><div dir=3D"auto">It would be =
interesting to set up integration tests wirh connections being disrupted in=
 various ways and at different moments during connection and query processe=
s. I&#39;d rather do them in a test framework rather than one-off.</div><di=
v dir=3D"auto"><br></div><div dir=3D"auto">Mitmproxy could be a nice tool t=
o build them.</div><div dir=3D"auto"><br></div><div dir=3D"auto"><a href=3D=
"https://mitmproxy.org/">https://mitmproxy.org/</a><br></div><div dir=3D"au=
to"><br></div><div dir=3D"auto">-- Daniele</div><div dir=3D"auto"><div clas=
s=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div dir=
=3D"ltr"><div><div dir=3D"ltr"></div></div></div></div>
</blockquote></div></div></div>

--000000000000c4c63905a20eedde--