Edge linking does not use index
|Reported by:||strk||Owned by:||strk|
I've found sequencial scans on the edge table during topology building which are due to the UPDATE queries to edges performed to set edge linking. The queries are of this form:
UPDATE topo_ulfareale.edge_data SET next_right_edge = -1175, abs_next_right_edge = 1175 WHERE edge_id != 1175 A ND next_right_edge = -1114;
But being there no index on next_right_edge the planner goes for a sequencial scan.
See also #2993 for skipping the UPDATE completely (but the SELECT query would still be needed so this ticket has its own right)