When running with threads >= 64 postgres dies during imports due to too many client connections at various stages. I recommend that the postgres config gets updated to something like 512 or 1024max connections just to be safe.
The first time I ran with 128 threads the image didn't make it past trying to load the ranks. It finished loading in the flat node file and died.
I ran it a second time with 64 threads and it failed again when importing the tiger data due to the same issue,. Unlike last time though it just sat there without actually proceeding.
Resolution
I manually went in, changed the max connections parameter, restarted postgres and imported everything else manually. Everything worked fine after that.
Bug
When running with threads >= 64 postgres dies during imports due to too many client connections at various stages. I recommend that the postgres config gets updated to something like
512or1024max connectionsjust to be safe.The first time I ran with 128 threads the image didn't make it past trying to load the ranks. It finished loading in the flat node file and died.
I ran it a second time with 64 threads and it failed again when importing the tiger data due to the same issue,. Unlike last time though it just sat there without actually proceeding.
Resolution
I manually went in, changed the max connections parameter, restarted postgres and imported everything else manually. Everything worked fine after that.
Desktop