osm2 pgsql primary key

[torecki]

Hi,
I dumped a germany.osm file with osm2pgsql in a postgresql database. It seems that osm2pgsql don’t make that one column is a primary key. I tryed to change the column osm_id so that the osm_id is the primary key. But than I get the message: The table contains dobble values.
I thought the osm_id should be unique…? Is the osm_id normally unique? Has anyone a hint for me to add a primary key into the databasetables?
Thanks
Torsten

[emj]

The postgis database has duplicates so just add a column which is unique.

OSM id are unique for each object type.
OSM id are never deleted, only marked invisble.

@Mailinglist

e.g.
http://www.openstreetmap.org/browse/way/10000000
http://www.openstreetmap.org/browse/node/10000000

You may not have encountered a problem with assuming A in a limited dataset as the ‘current’ value for ways is significantly smaller than for nodes and the current value for relations is significantly smaller than for ways due to there being a lot more ways than relations and a lot more nodes than ways…
From node and way stats:
Number of nodes 296115165
Number of ways 24186209
Number of relations 53679

[JRA (Jukka Rahkonen)]

Hi,

Osm2pgsql creates sometimes dublicate OSM_IDs. I have been thinking that they come usually from relations. I play with Finnish data and for me it is OK to set database to use WITH_OIDS as default and osm2pgsql can be used as is. Automatically created OID field is good for primary key. However, German subset may be so big that OIDs can not be used but another unique field should be made by hand.