Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

Editing data during planet.osm dump creates corrupt data #522

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 1 comment
Closed

Editing data during planet.osm dump creates corrupt data #522

openstreetmap-trac opened this issue Jul 23, 2021 · 1 comment
Assignees
@openstreetmap-trac
Labels
Component: website Priority: major Resolution: wontfix Type: defect

Comments

@openstreetmap-trac
Copy link

Reporter: andrew.honeypot[at]gmail.com
[Submitted to the original trac issue database at 10.21am, Thursday, 9th August 2007]

If I edit the OSM data while a planet.osm dump is taking place (i.e. early Wednesday morning in the UK), this causes the affected ways to be omitted from the planet.osm dump. This results in corrupt data in the planet.osm dump and the weekly Mapnik rendering.

Possible ways to prevent this:

  • Lock database during planet.osm dump
  • Use history to make planet.osm dump reflect the state of the database at 0:00 UTC on Wednesday morning, ignoring any edits that occured after that time
@openstreetmap-trac openstreetmap-trac self-assigned this Jul 23, 2021
@openstreetmap-trac
Copy link
Author

Author: tom[at]compton.nu
[Added to the original trac issue at 6.26pm, Wednesday, 15th August 2007]

Unfortunately I don't think there is much we can do about this - option 1 is clearly not possible and I suspect option 2 is not computationally feasible.

The correct solution would be to use transactions but (a) I have no idea if MySQL could cope with such a massive transaction and (b) half our tables are MyISAM tables which don't support transactions.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@openstreetmap-trac openstreetmap-trac

Labels
Component: website Priority: major Resolution: wontfix Type: defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@openstreetmap-trac