Help deciphering database error on indexing stage #2304
-
Hi all, I'm positive this isn't an osm2pgsql issue, but I'd like to ask if anyone could provide some pointers on where to look for the culprit. So... I'm trying to do an import of an extract for Africa into a DigitalOcean managed database; this is a 4vcpu, 8GB and 200 GB disk. The processing goes well and it's on the indexing stage that I'm getting disconnects from the database and I can quite pinpoint why. I've added Things I've looked for
If anyone can offer any hints, it would be much appreciated. osm2pgsql version was built from code.
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Have look into the logfile of PostgreSQL. The error usually means that the database was restarted. My guess here is that you have run out of memory. The log file should have details. Running an Africa import on 8GB RAM seems a bit tight to me. Consider switching to a machine with 16GB RAM. |
Beta Was this translation helpful? Give feedback.
Have look into the logfile of PostgreSQL. The error usually means that the database was restarted. My guess here is that you have run out of memory. The log file should have details.
Running an Africa import on 8GB RAM seems a bit tight to me. Consider switching to a machine with 16GB RAM.