Re: psycopg3: a first report

From: Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com>
To: Stefan Knecht <knecht(dot)stefan(at)gmail(dot)com>
Cc: Rory Campbell-Lange <rory(at)campbell-lange(dot)net>, psycopg(at)postgresql(dot)org
Subject: Re: psycopg3: a first report
Date: 2020-03-30 09:30:33
Message-ID: CA+mi_8a57tS19oxdN5LtToVd8mXZMwqNG1F8Q3qv+zvckx6N9g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: psycopg

>
> 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

In response to

Browse psycopg by date

  From Date Subject
Next Message Rory Campbell-Lange 2020-03-30 10:00:21 Re: psycopg3: a first report
Previous Message Daniele Varrazzo 2020-03-30 09:17:53 Re: psycopg3: a first report