I would say yes.
In my case I am not querying only sequence column.
I have the following cases which I want to optimize.
1. Select * from Some_table where job = <somthing> and nlp = <something> and year = <something> and scan_id = <something>
2. Select * from Some_table where job = <somthing> and nlp = <something> and year = <something> and Issue_flag = <something>
3. Select * from Some_table where job = <somthing> and nlp = <something> and year = <something> and sequence = <something>
Those are queries that my app send to db that is why I said that from read perspective our best case is 3 separate indexes for
(job, nlp, year, sequence) AND (job, nlp, year, Scan_ID) and (job, nlp, year, issue_flag) and any other solution like
(job, nlp, year, sequence, Scan_ID, issue_flag) OR (job, nlp, year ) INCLUDE(sequence, Scan_ID, issue_flag) OR just (job, nlp, year) can be considered as worst case
I will remind that in real world scenario I have ~50m rows and about ~5k rows for each (job, nlp, year )
