On Mon, 17 Oct 2022 at 13:08, Stefan Knecht wrote:
>> Which version of psycopg are you
>> using? Some old one have problems with closing connections in
>> multiprocess environments. That was fixed in psycopg 2.8 (#829).
>>
>
> This is psycopg 3.1.3
>
> And I just realized that all the other threa
Ah, the error was (of course) between the keyboard and the chair.
A database handle was defined on the thread class - not the instance. And
for some reason everything was still working, just with very unexpected
behavior :)
Have a good one Daniele
On Mon, Oct 17, 2022 at 7:13 PM Stefan Knecht
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 process (not some serverless thing?)
>>
>>
> I'
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
Hi Stefan,
On Mon, 17 Oct 2022 at 12:25, Stefan Knecht wrote:
>
> 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.
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
