[Tile-serving] [openstreetmap/osm2pgsql] Inconsistent use of --prefix (#904)
NopMap
notifications at github.com
Sun Jan 27 09:31:10 UTC 2019
Debuggin something else, I noted that the --prefix option seems not to be used for all actions during import. I am using osm2pgsql version 0.96.0 (64 bit id space)
I have some production tables planet_osm_* serving the rendering. The import takes place into background tables data_* with -p data.
During import into a fresh database where the planet_osm_* tables do not exist yet, I noted many error messages in the postgresql log with the same pattern:
`
2019-01-27 09:32:57.846 CET [8018] user at database ERROR: relation "planet_osm_point" does not exist at character 160
2019-01-27 09:32:57.846 CET [8018] user at database STATEMENT: SELECT osm_id, st_y(st_transform( ST_SetSRID(way, 900913), 4326)) as lat, st_x(st_transform( ST_SetSRID(way, 900913), 4326)) as lon, route_list_osmid
FROM planet_osm_point
WHERE way && st_transform( ST_SetSRID(ST_MakeBox2D(
ST_Point(6.821737289428711,45.825629378784384),
ST_Point(6.932115554809569,45.87106689912796)), 4326), 900913) and route_list_osmid is not NULL
`
It seems that some statements ignore the --prefix option "data" and are hard-coded to planet_osm_point.
If the planet_osm tables exist, there is no error message - but it means that osm2pgsql is mixing import data with data from the production tables.
Can you confirm this problem?
What sort of operation is using the above query?
What is the impact on the import when data is mixed in this way?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/osm2pgsql/issues/904
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tile-serving/attachments/20190127/b5705daf/attachment.html>
More information about the Tile-serving
mailing list