Opened 2 years ago

Closed 2 years ago

#5097 closed defect (fixed)

GetClosestEdge callback failing to use an index

Reported by: strk Owned by: strk
Priority: medium Milestone: PostGIS 3.2.2
Component: topology Version: 3.2.x
Keywords: performance Cc:

Description

As reported in ​https://github.com/postgis/postgis/pull/666 the getClosestEdge callback query is failing to use the gist index on edge_data due to the presence of a second column in the ORDER BY specification.

Change History (3)

comment:1 by strk, 2 years ago

Keywords: performance added
Milestone: PostGIS 3.3.0 → PostGIS 3.2.2

comment:2 by Sandro Santilli <strk@…>, 2 years ago

In 8288bd8/git:

Do not sort by edge_id in getClosestEdge callback, to effectively use index.

References #5097 in master branch (3.3.0dev)

comment:3 by Sandro Santilli <strk@…>, 2 years ago

Resolution: → fixed
Status: new → closed

In e9014f4/git:

Do not sort by edge_id in getClosestEdge callback, to effectively use index.

Closes #5097 in stable-3.2 branch (3.2.2dev)

Includes NEWS item

Note: See TracTickets for help on using tickets.