[Geocoding] Large index crashes postgres

Frans Hals fhals7 at googlemail.com
Wed Mar 24 20:25:15 GMT 2010


I feared that this problem may be unique in its kind.
I can't imagine there's a difference between indexing a dump and fresh import.
Postgis is handpicked for 8.3.9 and when I ask for index all rows
whose osm-id is below 100.000 all is well.
Now I tried the postgresql mailing list as you suggested in the hope
for a solution.
If I get any useful answer, I'll surely post it here.

Frans

2010/3/24 Brian Quinion <openstreetmap at brian.quinion.co.uk>:
> Sorry - but I'd love to know the answer if you get one!
>
>> Is there anybody else who experienced this and found a way to create this
>> index?
>
> No one else has had this problem that I'm aware of - but there are
> lots of combinations of postgresql and postgis versions.
>
> The only thought that does occur is that maybe, as a result of trying
> to load the database dump, you have ended up with a incompatible
> version of postgis loaded?
>




More information about the Geocoding mailing list