postgres bottleneck?

[balazsdukai]

batch3dfier reads the footprints from postgres views and opens a single connection for all the operations. Apparently prior version 9.6, postgres can only use one CPU thread/core at a time. I'm not sure about it, but this might mean that regardless of how concurrency is implemented, the bottleneck might become the I/O from postgres as it can only run on a single thread (because there is a single open connection). It seems like that this problem could be side-stepped by opening a separate postgres connection for each thread.