Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jIm1K-0002Vg-2n for psycopg@arkaria.postgresql.org; Mon, 30 Mar 2020 04:27:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jIm1I-0003Cp-OC for psycopg@arkaria.postgresql.org; Mon, 30 Mar 2020 04:27:28 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jIm1I-0003BC-IG for psycopg@lists.postgresql.org; Mon, 30 Mar 2020 04:27:28 +0000 Received: from mail-oi1-x22f.google.com ([2607:f8b0:4864:20::22f]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jIm1E-0001YI-Qz for psycopg@postgresql.org; Mon, 30 Mar 2020 04:27:28 +0000 Received: by mail-oi1-x22f.google.com with SMTP id k5so4959080oiw.10 for ; Sun, 29 Mar 2020 21:27:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=wcKruLmB+lkK6E8XoQ86i+BVlQVoIHu/AobzfYCnEpk=; b=hs982eAivYZ7qT2OJmF7yYzp5a2GMO+s0dNuNAT9QcSPkubA+aW0XIxq5py8AKTBs/ aAPwGmiP1heRrMARgg0pMvJWSIvxNSNM0HQCgBGVB53HLxFqOJnPqrXHv3gI9ZW/Wgpq TqAWMSzhyiiL6uUkJa0fUNAqVJFy9wosU9UfxjuIIUHhbVXctYmLtaX6nkerb8JdHCIG 3pnyRGrwU2xoV+OBXNPxD78Gz/K9il75PBeoiEUM97ZiBrPMoxS/zvyx35MXAZsoEnIL ++Ib5whMzQDz9HeQdacPNquDTatMYVuNjJA0xqA9QIRxCtBpc3WeTQ2GE/YOkJRGVMrp AHSQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=wcKruLmB+lkK6E8XoQ86i+BVlQVoIHu/AobzfYCnEpk=; b=OPt1Aln4VYkdyt5yQPKlYifti47vHbSvJ8uVHYz4EZX7aQJoflT45XorCXJWtks1SC aM8MFzBCmj6FvPup6quqmZ6/7Ju8SaZP4DRs6xpLCtVW8ATq/J7Q/KR2maPIv0egpR7f 1syiYfp3cr5Yhf1P1QhMZDnpPreE6t5qUJGI01Gd6p28H3/i/+WttcpCFxjypcvlvVZ0 FYByvZH0KZkWxe4pLqKJKbQqvAEATosZTGnRweJxTjLKZYhBpr2K73vZ0kQBwzglhbuu TJoNway5Wcn5emhGNTD7MjrdHa+jCd4D/zRq17ecUcwRp/o63k2yiWCvApet2pnyGoOC cs/A== X-Gm-Message-State: ANhLgQ12sW3J6PIdu2CdkSHePVLqWCwxtnUuMKJVEAaQai+UUqrTBm4M OMg2dG3ypmejTuQJRmCJzq9ApIwlN+H33kLF6zc= X-Google-Smtp-Source: ADFU+vuywqUC7RngMR6WoXdxfkO99OxBSNSTXSjeqBvMtixvF879OnEDV+85QLqly3y2eKjUBkl1dB4jGqiFjzGKCMM= X-Received: by 2002:aca:4d86:: with SMTP id a128mr6568881oib.96.1585542443029; Sun, 29 Mar 2020 21:27:23 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Stefan Knecht Date: Mon, 30 Mar 2020 11:27:13 +0700 Message-ID: Subject: Re: psycopg3: a first report To: Daniele Varrazzo Cc: psycopg@postgresql.org Content-Type: multipart/alternative; boundary="00000000000017d89e05a20ade7f" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --00000000000017d89e05a20ade7f Content-Type: text/plain; charset="UTF-8" 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 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/ --00000000000017d89e05a20ade7f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Ciao Daniele

Glad to see pro= gress 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 midd= le 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.varrazzo@gmail.com&g= t; 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<= br> 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= =C2=A0zztat.net=C2=A0| @zztat_oracle | fb.me/zztat | zztat.net/blog/
--00000000000017d89e05a20ade7f--