[Geocoding] osm2pgsql / Gazetteer import errors

[Frans Hals]

Thanks Brian,

I'm glad to hear that the import should be done faster on another
machine. It's just the more you wait for completion, the less you
won't stop it before.

I started the process on a standard Amazon cloud 32-bit 1-Processor Fedora unit.
So this may be a warning example for everybody else trying it.
When you talk about another 35 days, will this be the current
after-import-indexing or the indexing mentioned in step 6 of the
Readme?
> 6) Index the database - this will take a VERY long time!
> cat gazetteer-index.sql | psql gazetteer


If the current indexing is done, I will try to clone the machine image
to a bigger one and
start with paragraph 6. If you think, the current one will last again
some days, I'll stop it and restart on a bigger block.

By now I am here:

144182 | gazetteer |   29653 |       10 | postgres | COPY place FROM
STDIN
| f       | 2009-12-30 16:03:01.159557-05 | 20
09-12-30 16:06:20.203637-05 | 2009-12-30 16:03:01.156937-05 |
   |          -1
  11564 | postgres  |    1969 |       10 | postgres | select * from
pg_stat_activity;
 | f       | 2010-01-04 08:11:42.996739-05 | 20
10-01-04 08:11:42.996739-05 | 2010-01-04 08:11:37.171401-05 |
   |          -1
 144182 | gazetteer |   29658 |       10 | postgres | CREATE INDEX
planet_osm_ways_nodes ON planet_osm_ways USING gin (nodes
gin__int_ops); | f       | 2010-01-03 19:54:54.928636-05 | 20
10-01-03 19:54:54.928636-05 | 2009-12-30 16:03:01.394407-05 |
   |          -1
                                                    :

 144182 | gazetteer |   28416 |       10 | postgres | autovacuum:
ANALYZE public.planet_osm_ways
   | t       | 2010-01-03 19:56:45.038247-05 | 20
10-01-03 19:56:45.038247-05 | 2010-01-03 19:56:44.998037-05 |
   |

Thanks again
Frans


2010/1/4, Brian Quinion <openstreetmap at brian.quinion.co.uk>:
> On Mon, Jan 4, 2010 at 12:02 PM, Frans Hals <fhals7 at googlemail.com> wrote:
>> after 4 or 5 days of importing planet.osm I have found out, that the
>
> Are you still running osm2pgsql? or have you started the indexing process?
>
> If you are still just running osm2pgsql after 5 days then I'd suggest
> your hardware probably isn't up to a full planet import since the
> initial import is about 1/8th of the import process.  That would make
> the indexing on your system about another 35 days.  Feel free to try,
> but just warning you.
>
>> FATAL:  role "gis" does not exist
>> FATAL:  database "gazetteerworld" does not exist
>
> gis is the default database used by osm2pgsql.  It's possible that it
> tries to connect as this somewhere in the code but if it is still
> running my guess is that it isn't important.
>
> gazetteerworld is referenced in settings.php only (by mistake, I use
> both on the main server) try changing this back to 'gazetteer', but my
> guess is that again it isn't anything important - osm2pgsql doesn't
> reference this file at all.
>
>> Actually the postmaster is still working, while osm2pgsql is in idle.
>> Will there be a message when it is ready or am I finished when I see
>> the text below?
>
> Probably it is still creating indexes.
>
> Try doing a 'select * from pg_stat_activity;' using pgsql to see where
> it is up to.
>
> --
>  Brian
>