Lots of changes: improved OS X and FreeBSD support, ordering by GeoHash for imrpvoed performance, removal of support for 32 bit node IDs and GEOS 2, code cleanups to modern C++ code, and various bugfixes. - C++ cleanups - Fix lockfree queue implementation so --without-lockfree is no longer required - Convert tags to std::vector - Fix multi-backend node cache and tag processing - Autoconf macro updates - New multi-backend example - C++ cleanups - default.style cleanups to improve ease of modification - Remove the lockfree queue pending implementation and default to what was --without-lockfree, which uses less RAM - RAM node storage cleanups - Better node storage test coverage If upgrading and using a database created with 0.86.0 or earlier, the schema migrations in docs/migrations.md are required. Major changes since 0.86.0 - Osm2pgsql is now C++ and requires the Boost libraries - A new backend has been added, the “multi” backend. This allows multiple tables which can each contain different types of features. More documentation is available at docs/multi.md - In-database pending way tracking has been replaced with in-memory tracking, offering significant performance gains. - Rendering tables are ordered by GeoHash when created, resulting in significant performance improvements. - z_logic has been improved, taking into account more recent work across multiple styles. - The node storage has been improved, and out of order nodes and nodes at 0,0 should now always be handled correctly - A new test suite with unit tests - Many bug-fixes This maintainance release fixes duplicates in the job queues for pending ways and relations, minor compiler errors, and updates memory usage documentation. The duplicates in job queues (#419) only impacted multithreaded updates and was not observed in most cases.
author Amy Winston <amynka@gentoo.org> 2016-01-12 20:10:09 (GMT) committer Amy Winston <amynka@gentoo.org> 2016-01-12 20:10:09 (GMT) commit 3bf4ad99982d99c17e85516f3444fb3642e1f7fe sci-geosciences/osm2pgsql: 0.88.1 version bump bug #564496 Thanks
