New in DoctrineBundle 1.11.0

DoctrineBundle is the library that integrates the Doctrine DBAL and ORM
libraries into Symfony applications. DoctrineBundle 1.11.0 has just been
released and includes several new features and improvements. These are the most
important ones.

Using Symfony Cache pools for caching Doctrine's queries, metadata and
results is now easier thanks to the new pool option. This allows using a
Symfony Cache pool directly without having to create extra services:

Using the new pool setting is optional, as is the dependency on symfony/cache.
However, in the future, declaring caches through DoctrineCacheBundle will be
deprecated, leaving only the id and pool cache types. Support for
DoctrineCacheBundle will be dropped in DoctrineBundle 2.0.

If you are using the Messenger component, there are new middleware services
you can use to avoid connection issues to your database:

The doctrine_ping_connection middleware will attempt to ping the connection
and will reconnect to the database if this ping wasn't successful. It will
also reset the entity manager should it have been closed in the meantime.

The doctrine_close_connection middleware will close the connection after
handling a message.

Hm.. So I removed the two services defined by the DoctrineBundle recipe (https://github.com/symfony/recipes/blob/master/doctrine/doctrine-bundle/1.6/config/packages/prod/doctrine.yaml), doctrine.result_cache_provider, and doctrine.system_cache_provider and replaced the cache configuration witht he one shown above (as the recipe hasn't been updated) but now I get:

The service "doctrine.orm.default_entity_manager" has a dependency on a non
-existent service "doctrine.orm.cache.pool.doctrine.system_cache_pool".

Should I make this a ticket in the DoctrineBundle? As this new configuration above isn't mentioned there right now, I'm not sure if that would be the correct thing to do.

profiling_collect_backtrace ... Can we log backtrace when the query is slower than X ms? Something like the MySQL's slow log option. Such an option could provide a useful middle ground for development servers with only a little overhead.