us77ipis
us77ipis
There are 4 threads dead locked at this point: ``` #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x00007ffff32cee4e in QSemaphore::acquire(int) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x00007fff7ccf8529 in QgsConnectionPoolGroup::acquire(int, bool) (this=0x555556304a70, timeout=-1, requestMayBeNested=false)...
Seems like the 4 threads mentioned above each acquire a lock on a database connection for the layer B, and then all 4 threads want to acquire another database connection...
Why even does QGIS do nested SELECTS when it joins two layers of database tables from the same source. Why no real JOIN at database level? This gives N+1 SELECTS...
What about https://hub.docker.com/r/timescale/timescaledb-ha ?
Similar issue here using `MatDialog`, though nested: I can `inject` a service in the dialog component itself alone and it works, however if I have a nested component used inside...
Same issue here with `timescale/timescaledb-ha:pg16`.
For me it is working now again with `timescale/timescaledb-ha:pg16` too.