>I checked a few minutes ago and the index is still optimized. It has preserved it longer than the last few days. So, it might well be that the single index was causing the new one to be destabilized faster as the table grows.
>
>If that remains as is, I will then remove the indexing at midnight for a while to see if it can be preserved as is.

Hi Michel,

Do you know which queries use(d) the other index? We discussed this issue a bit more with Denis. He is suggesting to create this index with DESC sort for the best performance. So, your other queries also use it in DESC order, it will make sense. Or have this index in DESC sort and restore the original index?