[OSM-dev] osm2pgsql: "unexpected chunk size"
Jon Burgess
jburgess777 at googlemail.com
Thu Jun 5 10:18:52 BST 2008
2008/6/5 Frederik Ramm <frederik at remote.org>:
> Hi,
>
> what does it mean when I get the following error message (last line)
> when running osm2pgsql on a current planet? Is it one of these "retry,
> then reinstall PostGIS from scratch" problems? Have I simply run out of
> memory?
>
> Bye
> Frederik
>
>
> Using projection SRS 900913 (Spherical Mercator)
> Setting up table: planet_osm_point
> Setting up table: planet_osm_line
> Setting up table: planet_osm_polygon
> Setting up table: planet_osm_roads
> Mid: Ram, scale=100
>
> Reading in file: /mnt/raid/planetfiles/current-planet.osm
> Processing: Node(242394k) Way(19602k) Relation(10k)
> Node stats: total(242394514), max(268375836)
> Way stats: total(19602070), max(24690151)
> Relation stats: total(10926), max(15735)
>
> Writing way(1340k)
> ANALYZE planet_osm_line;
> CREATE TABLE tmp AS SELECT * FROM planet_osm_line ORDER BY way;
> DROP TABLE planet_osm_line;
> ALTER TABLE tmp RENAME TO planet_osm_line;
> CREATE INDEX planet_osm_line_index ON planet_osm_line USING GIST (way
> GIST_GEOMETRY_OPS);
> GRANT SELECT ON planet_osm_line TO PUBLIC;
> ANALYZE planet_osm_line;
> failed: ERROR: unexpected chunk size 178401435 in chunk 0 for toast
> value 1969418
>
> _______________________________________________
> dev mailing list
> dev at openstreetmap.org
> http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/dev
>
Looks like an error from PostgreSQL. I would guess a disk space or
memory problem first. Might worth trying to import a smaller .osm
saved from Josm as a quick test.
--
Jon
More information about the dev
mailing list