[Geocoding] Large index crashes postgres

[Frans Hals]

Brian,

this is what I got back from the postgresql list:

>OK, must be a leak somewhere in those functions, small but enough to
>make a difference over a large number of records.  I've made a ticket
>for the issue,

>http://trac.osgeo.org/postgis/ticket/470

>Could you
>- put in your version information
>- tell me what kind of spatial objects you have? polygons of > 100
>vertices? lines of two vertices? etc. That will help me pick similar
>data for the memory testing.

Strange, that I'm the only one running into this.
Do you know the answer of the last question above?


2010/3/24 Brian Quinion <openstreetmap at brian.quinion.co.uk>:
> 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?