CI quickstart test random failure

[rebasedming]

What happens?

The following query in CI:

SELECT description, rating, category, paradedb.score(id)
    FROM mock_items
    WHERE description @@@ 'shoes' OR category @@@ 'footwear' AND rating @@@ '>2'
    ORDER BY score DESC, description
    LIMIT 5

Fails because the fifth row matches "Winter woolen socks" instead of "Sturdy hiking boots." This is not correct -- ordering by description should sort by alphabetical order.

To Reproduce

Haven't produced locally, but seeing sporadic CI failures.

OS:

Ubuntu

ParadeDB Version:

0.12.1

Are you using ParadeDB Docker, Helm, or the extension(s) standalone?

ParadeDB pg_search Extension

Full Name:

Ming

Affiliation:

ParadeDB

Did you include all relevant data sets for reproducing the issue?

Yes

Did you include the code required to reproduce the issue?

• [X] Yes, I have

Did you include all relevant configurations (e.g., CPU architecture, PostgreSQL version, Linux distribution) to reproduce the issue?

• [X] Yes, I have

[eeeebbbbrrrr]

This is because this is a "top N" query, which only selects the top N based on the score. When two documents in the top N have the same score, the order in which they're returned is undefined.

While not exactly intuitive, this is by design.

The only fix for this would be to turn off the "top N" optimization if there's multiple sorts. This is effectively the "tie break" problem.