Question: When ES is working for files and deck provider how to switch off DB operation for those providers?

[cue108]

I now have an Elasticsearch (ES) cluster up and running, and a full indexing process completed successfully. As expected, I'm getting very fast results from the ES cluster. However, when monitoring the system, I've noticed that the database operations for provider file searches are still running and taking a long time. This is putting a heavy load on the database and significantly affecting the overall responsiveness of the system, even for a single search.

Moreover, when using the search via the Nextcloud App or also via the Nextcloud Desktop App a result can only be clicked when the whole search is done.
Usually the ES based searches for the provider file and deck are instantly responding while for the provider files via DB operations on both the smartphone apps and the desktop apps takes minutes on my system and in the meantime I cannot choose the results I can see on the screen already. So I have to stare on the desired search results while waiting until the DB operation for files delivering less results is processing for-ever..

I would like to disable the database-based search since I'm highly satisfied with the results provided by ES. How can I achieve this?

[cue108]

Improved DB behavior via replacing slow indexes on oc_filecache under Postgres with appropriate once.