[OSM-dev] vacuum running amok - and me too ;)

[Paul Norman]

On 3/9/2015 7:34 AM, Walter Nordmann wrote:
> *Vacuum planet_osm_ways*  is using very, very much memory vacuuming the
> GIN-Index planet_osm_ways_nodes.

Indexes aren't vacuumed, tables are. Are you vacuuming the table or
rebuilding theindex?

If you have autovacuum tuned aggressively enough there should be no
need to manually vacuum the slim tables. The GIN indexes do tend to
bloat, and this can be fixed by stopping updates, dropping the old
index and building a new one. It would be surprising if this results
in PostgreSQL being killed by the OOM killer, asit has to execute
the same statements when importing.

A better approach might be to re-import with a different name, then
when that import is done drop the old database and rename the new one.