Open Zverik opened 1 month ago
That's an osm2pgsql issue. Because you imported with Nominatim 4.3.2, you are stuck with the old middle format and it looks like it still has issues with large diffs. Try a catch-up with very small diffs, something like NOMINATIM_REPLICATION_MAX_DIFF=500.
Thanks Sarah. Small diffs didn't work, so reimporting the database from scratch with 4.4.0. Turns out updates for another server (that's on 4.3.2 and imported in January) already stuck three weeks ago :(
The server stuck three weeks ago is likely #3445. This new server isn't because the planet is post vandalism. So I suspect you have two unrelated problems here. You could try running an 'ANALYSE' on the new database and see if that helps.
(Also note that I'm intentionally not closing this ticket. Still investigating what is exactly going on.)
Right. I'll see how it goes and report back to you :) Until the second server is in production, we could run any tests on it.
So. I have imported the planet again (same one) with Nominatim 4.4.0, and everything went fine, including the catch-up update. Probably because the planet file was generated after the vandalism wave. Feel free to close this ticket when you don't need it :) And thank you for the hint about differing osm2psql versions.
I have installed Nominatim, did a full planet-240624 import, but on
replication --catch-up
it hangs while reading the data. It looks like #3445, but in some ways different.Log file is:
(and stuck on this line and count).
In psql, this is the stuck query:
Software Environment (please complete the following information):
Hardware Configuration (please complete the following information):
Nominatim Configuration: