Each session maintains a cache of table handles. These are separate to the data handles for btrees – each table is opened again, and a structure populated, by each session that accesses the table.
In applications that access many tables, the table cache can become large. Old tables should be cleared from the cache to avoid an unexpected accumulation of memory.
- is related to
-
SERVER-30492 Drop can fail because it is run in a session with cached cursors
-
- Closed
-
- related to
-
-
- Closed
-
- links to