Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 2.0.1
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
For most databases prepared statement caching is sort of cheap. For Oracle, it's not, each prepared statement keeps a cursor open on the server side.
Cursors are usually limited by admins being expensive resources to keep around.
Expose a property to limit the number of cached prepared statements.
Limitless does not sound very good in general, we may want to provide this property for any database that uses prepared statements.
Issue Links
- depends upon
-
GEOT-2893
Unbounded prepared statement pooling can bring Oracle to its knees
-
The default could be 50 per connection, if set to 0 or less than 0 we could stop caching them. Don't really think we need a way to express "limitless" in the configuration, one can always specify a very high number and get to the same result (e.g., 10000 per connection)