planet_osm_nodes table without index and no PK constraint

[dbt-lucka]

Hi,

after a lot of debugging why my nominatim replication takes more than 24h to catch up with 4 days of data, I compared my Full Europe-imports indexes list with a one from a very small German state.

It turned out that this index is missing:

CREATE UNIQUE INDEX planet_osm_nodes_pkey ON public.planet_osm_nodes USING btree (id);

I noticed because the Query Insights in Google Cloud show minute-long queries on that table.

I am creating that index manually now and then I expect this issue to resolve. However I wanted to share this anyhow.
I couldn't notice this index from being skipped at pg_restore and I suppose if there would had been an error at this step, the pg_restore would have failed completely, right?

[dbt-lucka]

Further investigating on this and I found the root cause. It's described in this PR.