[Tile-serving] [openstreetmap/osm2pgsql] Enable lossy way-node indexes by default? (Issue #1687)

[mboeringa]

The question may be as to what the option is trying to solve? 

2TB NVMe can nowadays be had for as little as $140,-, so performant disk space really shouldn't be that much of an issue today... 

If the 200GB disk space saved is worth the 30% performance penalty for updates, as [@joto mentioned](https://github.com/openstreetmap/osm2pgsql/pull/1275#issue-707365815) in the other issue, therefor needs to be weighted.

Maybe extending your question with another one "Do people still feel (indexing) disk space is an issue nowadays with osm2pgsql import/updates?" might help to clear it up.

Another unanswered question is the one I posted [here](https://github.com/openstreetmap/osm2pgsql/pull/1275#issuecomment-704735678), whether the performance hit only affects updates, or also initial imports?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/osm2pgsql/issues/1687#issuecomment-1166572081
You are receiving this because you are subscribed to this thread.

Message ID: <openstreetmap/osm2pgsql/issues/1687/1166572081 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tile-serving/attachments/20220626/af3f4aae/attachment.htm>