Sorry, I had dropped the db and started all over. Interestingly, I now have
254GiB free out of initially 669, so the DB is using 415GiB. Note that the
import used 198 extra GiB while clustering, which still matches the ~10x
imported, ~15x while importing numbers I got a couple of years ago:
https://www.grulic.org.ar/~mdione/glob/posts/disk-usage-while-importing-an-osm-rendering-database/
So in my impression, the updates are somehow using more space. Assuming the
update does a VACUUM at the end, I would expect a failed update's extra space
to be reclaimed after a subsequent successful one (after freeing some space, of
course). I'll keep an eye on the updates for a week, then run a VACUUM, then
report here.
--
Reply to this email directly or view it on GitHub:
https://github.com/osm2pgsql-dev/osm2pgsql/discussions/2355#discussioncomment-13749614
You are receiving this because you are subscribed to this thread.
Message ID:
<osm2pgsql-dev/osm2pgsql/repo-discussions/2355/comments/[email protected]>
_______________________________________________
Tile-serving mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/tile-serving
