The problem here appears to be due to the new approach to batch loading on Postgres.
So the workaround would be to disable batch loading, I imagine.