More sorting options

[admtech]

What
The default sorting for "pg_search" is always BM25 scoring. In general, relevance is of course the first and most important sort. However, our users have expressed a desire for further sorting, e.g. by timestamp . This means showing all content with the search terms, but then by timestamp and not by relevance.

Why
This does not work optimally at the moment because there is no additional sorting field. Even if the TIMESTAMP field e.g. "stamp" is available in the index, I cannot use it for sorting. This means that I have to search the entire index first in order to re-sort with ORDER BY. The performance is not optimal for many sessions.

How
The ability to add a custom sort order. Any field that is also defined in the index should be able to be used as a sort field. Elasticsearch does this as well.

[rebasedming]

Looks like the solution is for us to expose Tantivy's order_by_fast_field. https://docs.rs/tantivy/latest/tantivy/collector/struct.TopDocs.html#method.order_by_fast_field

I can take this on over the next few days.

[colexbruhn]

I can take this on over the next few days.

Awesome, I was just looking to see if there was a better way to do this. For my use-case, I'd like to find relevant documents using bm25 and then sort them relative to user ratings. This is nice to have when user queries don't have enough content/context for semantic vector search.

[philippemnoel]

I can take this on over the next few days.

Awesome, I was just looking to see if there was a better way to do this. For my use-case, I'd like to find relevant documents using bm25 and then sort them relative to user ratings. This is nice to have when user queries don't have enough content/context for semantic vector search.

Thanks for sharing. We'll look to prioritize this soon