Hugh Saalmans

It's pointing towards being a multiprocessing issue related to the use of a Postgres connection pool. More investigation required as all connections should be running independantly in each process.

I've reverted the Postgres connect pool used in multiprocessing in favour of "standard" PG connections per process. There's evidence that Psycopg connection pools aren't multiprocess-safe. There's only a small impact...

The new release is done and in master. Please test.

The (now updated) readme was missing a note to download the GDA94 Shapefile version of the Admin Bdys (not the GDA2020 ones)! Please try again with the GDA94 files

Odd error! A couple of things to check: 1. The PostGIS extension is enabled on your database (using the following SQL - `CREATE EXTENSION postgis`); and 2. The Postgres bin...

One more thing to double check - have you got the latest code? The August 2021 release PR was this morning, Sydney time, and there have been a couple of...

Interesting - the code should import SHP files of the same layer (e.g town points) sequentially, so PG shouldn't be locking the table. I'll go with it being a knock-on...

Ok, so shp2pgsql worked, but the table missing the geom field is very strange... I'm short of ideas right now as I've run this multiple times over the last few...

The table is created by the first state to be loaded for each layer. So `ACT_TOWN_POINT_shp.shp` should create the table `aus_town_point` with that file's structure. The `-d `flag in _shp2pgsql_...

Cool, we've got the problem nailed down. Curious that the behaviour is different between operating systems, but not as important as finding a universal fix... I've just updated the code...