[Tile-serving] [osm2pgsql-dev/osm2pgsql] Update behaviour after disk is full. (Discussion #2355)

Paul Norman notifications at github.com
Sat Jul 12 23:00:46 UTC 2025


This is all up to PostgreSQL as osm2pgsql's only direct usage of disk space is the flat nodes file. When importing data twice on the second import it will delete rows then insert new rows with identical contents. This consumes disk space.

You should run a vacuum. You probably don't have enough room for a vacuum full or cluster.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/osm2pgsql-dev/osm2pgsql/discussions/2355#discussioncomment-13741117
You are receiving this because you are subscribed to this thread.

Message ID: <osm2pgsql-dev/osm2pgsql/repo-discussions/2355/comments/13741117 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tile-serving/attachments/20250712/577f4353/attachment.htm>


More information about the Tile-serving mailing list