Hi, On Sat, Jul 04, 2015 at 10:58:46AM +0100, Simon Nuttall wrote: > > > > I notice that our postgresql.conf has > > > > work_mem = 512MB > > > > which seems a bit small?
That's more than enough. I generally keep the value below 200MB as there might be many concurrent processes each using that much work_mem when queries come in. > > But this seems healthy: > > maintenance_work_mem = 10GB This has pretty much only relevance for vacuuming after the import. > Just a few more questions... > > I'll need to restart postgres to have some config changes take effect > so this means I'll need to interrupt the updates. > > During the > > ./utils/update.php --import-osmosis-all --no-npi --osm2pgsql-cache > 24000 --index-instances 2 > > phase can I stop it at anytime with Ctrl+C ? > > Or only when I am seeing lines like.. > > Done 929 in 147 @ 6.319728 per second - Rank 26 ETA (seconds): 801.616821 At this point is absolutely safe but in theory any other point is ok as well, at least I've never seen any problem. You should be aware though, that at other points some work might have to be re-done. This is in particular true whe osm2pgsql runs. It will roll back all changes when it is canceled. > To resume do I just use the same command or do I have to do anything else > first? Same command, it will automatically pick up at the right point. Sarah _______________________________________________ Geocoding mailing list [email protected] https://lists.openstreetmap.org/listinfo/geocoding
