On 28/02/2022 13:18, Alex Peshkoff via Firebird-devel wrote: > I suppose it's with mentoned 2Mb cache.
Yes. But it's the same even with 100K as the test uses very few and small statements. > > One more question. Suppose some statement remains in a cache for very > long time cause it's reused again and again. That's fine - but with DB > grow optimal plan can change. Is it solved somehow? Suppose in first > implementation not, Correct. And it's a problem also now when application holds prepared statement manually, but that probably is not going to be changed. > but are there plans to solve it? > I think there are two possible ways: - Timeout of cached statement (counting from its first appearance in cache, not last usage) - When engine detects a condition which could change a plan, it may ask cache for invalidation. Adriano Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
