diff --git a/Documentation/routers/SchemaRouter.md b/Documentation/routers/SchemaRouter.md index d1de66b2b..36df5244b 100644 --- a/Documentation/routers/SchemaRouter.md +++ b/Documentation/routers/SchemaRouter.md @@ -48,6 +48,8 @@ The schemarouter supports the following router options: --------------------------------------------- |max_sescmd_hitory | |Set a limit on the number of session modifying commands a session can execute. This sets an effective cap on the memory consupmtion of the session.| |disable_sescmd_history||Disable the session command history. This will prevent growing memory consumption of a long-running session and allows pooled connections to MaxScale to be used. The drawback of this is the fact that if a server goes down, the session state will not be consistent anymore.| +|refresh_databases|true, false|Enable database map refreshing mid-session. These are triggered by a failure to change the database i.e. `USE ...``queries. +|refresh_interval||The minimum interval between database map refreshes in seconds. ## Limitations The schemarouter router currently has some limitations due to the nature of the sharding implementation and the way the session variables are detected and routed. Here is a list of the current limitations.