At our company, we build applications managing big database, writing tons of log.
Detecting the cause of a database performance issue when you have thousands of requests per second is a nightmare.

I know many developers that would neglect a log of warn level of this kind.
Moreover, if the issue is introduced on a new table, performance deteriorations could begin to be perceptible more than a year later with data growth. Meanwhile, the bug would have been deployed in multiple customer instances.

I think that if a company or any kind of organisation considers that this as a serious thread, a configuration flag disabled would be great to tackle the issue at its root.