[Potlatch-dev] [OpenStreetMap] #4728: freeze after Ctrl+C during editing
#4728: freeze after Ctrl+C during editing ---+ Reporter: hwi@… | Owner: potlatch-dev@… Type: defect | Status: new Priority: minor | Milestone: Component: potlatch2 |Version: 2.0 Keywords: freeze Ctrl+C | ---+ because it happened twice during editing this afternoon: After having drawn a few new building polygons I wanted to add the streetname. I selected the street geometry, selected the street name in the property table and pressed Ctrl+C. Then potlatch2 froze completely: no reaction, no way to save the changes. I had to kill Firefox and terminate the Flash process in the Task Manager. My environment is: - Firefox 17.0.1 - Adobe Flash Player 11.5 r502 (in Task Manager: FlashPlayerPlugin_11_5_502_135.exe *32 ) - Windows 7 64 bit Has anyone seen this effect before? best regards hwi -- Ticket URL: https://trac.openstreetmap.org/ticket/4728 OpenStreetMap http://www.openstreetmap.org/ OpenStreetMap is a free editable map of the whole world ___ Potlatch-dev mailing list Potlatch-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/potlatch-dev
[osmosis-dev] production site disk use question
Are there any rules of thumb about Postgres disk requirements when importing osm data? For example, I just tried importing a 1.7GB planet-reduced.pbf into my rails port osm db and it failed after ~30 hrs because I ran out of disk space after it had eaten up 50GB of disk. Bad planning on my part, but how should I budget for this? e.g. a 30GB .osm file will probably take 2x that when the import is finished? Thanks, Jeff -- Jeff Meyer Global World History Atlas www.gwhat.org j...@gwhat.org 206-676-2347 ___ osmosis-dev mailing list osmosis-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/osmosis-dev
[OSM-dev] production site disk use question
Are there any rules of thumb about Postgres disk requirements when importing osm data? For example, I just tried importing a 1.7GB planet-reduced.pbf into my rails port osm db and it failed after ~30 hrs because I ran out of disk space after it had eaten up 50GB of disk. Bad planning on my part, but how should I budget for this? e.g. a 30GB .osm file will probably take 2x that when the import is finished? Thanks, Jeff -- Jeff Meyer Global World History Atlas www.gwhat.org j...@gwhat.org 206-676-2347 ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] production site disk use question
Le lundi 31 décembre 2012 18:25:28, Jeff Meyer a écrit : Are there any rules of thumb about Postgres disk requirements when importing osm data? Here is a table referencing disk size use by different osm database schema : http://wiki.openstreetmap.org/wiki/FR:Servers/Comparatif_des_formats_de_base_de_donn%C3%A9es#Comparatif osmosis schema takes 500Go of disk space for the planet file of 2012-09-15 -- sly (sylvain letuffe) ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
