Replies: 1 comment 1 reply
|
Bloat is "created" when things change. So I would assume that that's because there are more changes to the line table than to other tables. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
On a classic osm2pgsql setup (without flex), I've always seen that the planet_osm_line is the one that accumulates bloat compare to planet_osm_point or planet_osm_polygon.
Has anybody tried to explain this ?
I imagine it comes from PG/postgis level, not osm2pgsql itself.
Is this something that also happen on flex tables containing linestrings ?
All reactions