public inbox for [email protected]
help / color / mirror / Atom feedFrom: Daniele Varrazzo <[email protected]>
To: Stefan Knecht <[email protected]>
Cc: Rory Campbell-Lange <[email protected]>
Cc: [email protected]
Subject: Re: psycopg3: a first report
Date: Mon, 30 Mar 2020 22:30:33 +1300
Message-ID: <CA+mi_8a57tS19oxdN5LtToVd8mXZMwqNG1F8Q3qv+zvckx6N9g@mail.gmail.com> (raw)
In-Reply-To: <CAP50yQ9WSB6s_rfXe2S0V-8H8ByCRNSw6ninrGdn5NgLzWZ8bA@mail.gmail.com>
References: <CA+mi_8ZH-feQP0+k_j7_joygE=hMZCFnaNMv8Z1KCLKB9YLb0w@mail.gmail.com>
<CAP50yQ_Mt=RtR0sXYoazJTuarphR1Kv8A6YTevCMiv+xZeD9=Q@mail.gmail.com>
<[email protected]>
<CAP50yQ9WSB6s_rfXe2S0V-8H8ByCRNSw6ninrGdn5NgLzWZ8bA@mail.gmail.com>
>
> Having the client provide general handling for in-flight timeouts would be
> the overall best solution imho.
>
I agree on this: the client should be aware of timeouts, both on connection
and querying.
If we keep the waiting loops in Python and only use non-blocking C
functions I think making sure every operation has a timeout is achievable.
-- Daniele
view thread (8+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: psycopg3: a first report
In-Reply-To: <CA+mi_8a57tS19oxdN5LtToVd8mXZMwqNG1F8Q3qv+zvckx6N9g@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox