Knecht
wrote:
> Exact same behavior with psycopg2-binary 2.9.4.
>
>
>
> On Mon, Oct 17, 2022 at 7:08 PM Stefan Knecht
> wrote:
>
>> Ciao Daniele
>>
>> Thanks for looking at this.
>>
>>
>>
>>> I understand this happens on RDS. Does it
Exact same behavior with psycopg2-binary 2.9.4.
On Mon, Oct 17, 2022 at 7:08 PM Stefan Knecht
wrote:
> Ciao Daniele
>
> Thanks for looking at this.
>
>
>
>> I understand this happens on RDS. Does it happen on normal Postgres
>> too, from a normal proc
Ciao Daniele
Thanks for looking at this.
> I understand this happens on RDS. Does it happen on normal Postgres
> too, from a normal process (not some serverless thing?)
>
>
I'll test this now.
> Are there processes/forks involved?
No, just Python's basic threading.
> Which version of psyc
Hello
I have this situation now, that I can't wrap my head around and I'm hoping
someone can shed some light onto what is going on, before I spend hours
trying to reproduce this by taking the code apart into a test case.
A few facts:
- I've got a piece of code split into several classes.
- It in
onitoring
tools which are written in Python).
Having the client provide general handling for in-flight timeouts would be
the overall best solution imho.
On Mon, Mar 30, 2020 at 2:48 PM Rory Campbell-Lange
wrote:
> On 30/03/20, Stefan Knecht (knecht.ste...@gmail.com) wrote:
> > If I may,
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 mi
