Changing order of WHERE params changes performance dramaticaly

[starinacool]

Describe the bug
Query performance depend on WHERE parameters order

To Reproduce
Steps to reproduce the behavior:

1. Run queries changing order of params

Expected behavior
Performance does not depend on params order

Describe the environment:
Manticore 6.2.12 dc5144d@230822
Linux manticore-002 6.1.0-13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.55-1 (2023-09-29) x86_64 GNU/Linux

Messages from log files:
Messages from searchd.log and query.log (if applicable).

Additional context

select id,name from listing2 where is_reposted=0 and salesman=361813 and beg_date>1701251485 ORDER by name asc LIMIT 0,1000 OPTION ranker=none, cutoff=10000, retry_count=5, retry_delay=100, max_predicted_time=10, max_matches=1000; SHOW META;

Empty set (0.033 sec)

+---------------------+------------------------------------------------------------------+
| Variable_name       | Value                                                            |
+---------------------+------------------------------------------------------------------+
| total               | 0                                                                |
| total_found         | 0                                                                |
| total_relation      | eq                                                               |
| time                | 0.032                                                            |
| local_fetched_docs  | 0                                                                |
| local_fetched_hits  | 0                                                                |
| local_fetched_skips | 0                                                                |
| predicted_time      | 0                                                                |
| index               | is_reposted:SecondaryIndex (100%), salesman:SecondaryIndex (20%) |
+---------------------+------------------------------------------------------------------+

Now lets put salesman to the front of WHERE section:

select id,name from listing2 where salesman=361813 and is_reposted=0 and beg_date>1701251485 ORDER by name asc LIMIT 0,1000 OPTION ranker=none, cutoff=10000, retry_count=5, retry_delay=100, max_predicted_time=10, max_matches=1000; SHOW META;

+---------------------+------------------------------------------------------------------+
| Variable_name       | Value                                                            |
+---------------------+------------------------------------------------------------------+
| total               | 0                                                                |
| total_found         | 0                                                                |
| total_relation      | eq                                                               |
| time                | 0.003                                                            |
| local_fetched_docs  | 0                                                                |
| local_fetched_hits  | 0                                                                |
| local_fetched_skips | 0                                                                |
| predicted_time      | 0                                                                |
| index               | salesman:SecondaryIndex (100%), is_reposted:SecondaryIndex (20%) |
+---------------------+------------------------------------------------------------------+

salesman attribute has much higher cardinality.

[glookka]

Please provide index or source data that we can use to reproduce this behavior.