From: | Stefan Knecht <knecht(dot)stefan(at)gmail(dot)com> |
---|---|
To: | Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com> |
Cc: | psycopg(at)postgresql(dot)org |
Subject: | Re: psycopg3: a first report |
Date: | 2020-03-30 04:27:13 |
Message-ID: | CAP50yQ_Mt=RtR0sXYoazJTuarphR1Kv8A6YTevCMiv+xZeD9=Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | psycopg |
Ciao Daniele
Glad to see progress being made! Well written blog!
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.
Stefan
On Fri, Mar 27, 2020 at 5:46 PM Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com>
wrote:
> Hello,
>
> I have started working on psycopg3. Database communication is up and
> running, sync and asyncio, and now I'm busy with the definition of the
> adaptation layer.
>
> You can read more at
> https://www.varrazzo.com/blog/2020/03/26/psycopg3-first-report/
>
> Comments are welcome. Cheers!
>
> -- Daniele
>
>
>
--
//
zztat - The Next-Gen Oracle Performance Monitoring and Reaction Framework!
Visit us at zztat.net | @zztat_oracle | fb.me/zztat | zztat.net/blog/
From | Date | Subject | |
---|---|---|---|
Next Message | Rory Campbell-Lange | 2020-03-30 07:49:17 | Re: psycopg3: a first report |
Previous Message | Daniele Varrazzo | 2020-03-27 10:46:09 | psycopg3: a first report |