[PostGIS] #5903: topology/test/regress/topogeo_addlinestring test_224_out: ERROR: index returned tuples in wrong order
PostGIS
trac at osgeo.org
Mon May 26 02:04:53 PDT 2025
#5903: topology/test/regress/topogeo_addlinestring test_224_out: ERROR: index
returned tuples in wrong order
----------------------+---------------------------
Reporter: myon | Owner: pramsey
Type: defect | Status: new
Priority: high | Milestone: PostGIS 3.5.4
Component: postgis | Version: 3.5.x
Resolution: | Keywords:
----------------------+---------------------------
Comment (by strk):
The code block in PostgreSQL triggering the error seems to be only
triggered when there's a RECHECK directive:
{{{
/*
* Was the ORDER BY value returned by the index accurate? The
* recheck flag means that the index can return inaccurate
values,
* but then again, the value returned for any particular tuple
* could also be exactly correct. Compare the value returned
by
* the index with the recalculated value. (If the value
returned
* by the index happened to be exact right, we can often avoid
* pushing the tuple to the queue, just to pop it back out
again.)
*/
cmp = cmp_orderbyvals(node->iss_OrderByValues,
node->iss_OrderByNulls,
scandesc->xs_orderbyvals,
scandesc->xs_orderbynulls,
node);
if (cmp < 0)
elog(ERROR, "index returned tuples in wrong order");
else if (cmp == 0)
was_exact = true;
else
was_exact = false;
}}}
--
Ticket URL: <https://trac.osgeo.org/postgis/ticket/5903#comment:3>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.
More information about the postgis-tickets
mailing list