WARNING: there is no transaction in progress
Hi there
I'm getting a list of warnings from PostgreSQL during the import process. They don't break the import procedure, but it could be a sign of that something goes wrong. My osm2pgsql command is:
$ osm2pgsql --create --slim --cache 2000 <database-info> file.pbf
and output has lots of the warnings like that:
WARNING: there is no transaction in progress
Committing transaction for planet_osm_line
WARNING: there is no transaction in progress
Committing transaction for planet_osm_polygon
WARNING: there is no transaction in progress
Committing transaction for planet_osm_roads
WARNING: there is no transaction in progress
Committing transaction for planet_osm_point
WARNING: there is no transaction in progress
Committing transaction for planet_osm_line
WARNING: there is no transaction in progress
Committing transaction for planet_osm_line
WARNING: there is no transaction in progress
Committing transaction for planet_osm_polygon
WARNING: there is no transaction in progress
Committing transaction for planet_osm_roads
WARNING: there is no transaction in progress
Committing transaction for planet_osm_point
WARNING: there is no transaction in progress
Committing transaction for planet_osm_line
WARNING: there is no transaction in progress
Committing transaction for planet_osm_polygon
WARNING: there is no transaction in progress
Committing transaction for planet_osm_roads
WARNING: there is no transaction in progress
Committing transaction for planet_osm_point
WARNING: there is no transaction in progress
Committing transaction for planet_osm_line
WARNING: there is no transaction in progress
Committing transaction for planet_osm_polygon
...
This is expected.
I'm leaving it open because we don't have any open issues about if we can stop these COMMIT;s
FWIW, I have the same behavior.
This can only happen in updates nowadays and even then it should be rare. The problem is that we create lots of threads for stage 1b and then only one or two items to process come in. We should still fix that at some point.
Since e64d8fde we are not doing any explicit commits any more, so I believe this has been fixed long ago. Closing here. Please open a new issue if this happens again.