[doc][2024.2.1] Added limitations for YSQL Connection Manager #25458
Conversation
|
|
✅ Deploy Preview for infallible-bardeen-164bc9 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
|
||
| ## Limitations | ||
|
|
||
| - Changes to default GUC values for a user or database (ALTER ROLE SET/ALTER DATABASE SET queries) may reflect in other pre-existing active sessions. |
There was a problem hiding this comment.
can you be more specific? only flags, not YSQL configuration parameters, are listed above - so what values are you talking about?
There was a problem hiding this comment.
GUC values have nothing to do with anything previously mentioned on this page; this category of session-specific database objects may not have the correct behaviour when using connection manager as per the limitation I have mentioned. I also use the term "may" on this line because trying to explain the scenario(s) where this behaviour can be seen would dive into too many technical details for what is a very rare corner case.
docs/content/stable/explore/going-beyond-sql/connection-mgr-ysql.md
Outdated
Show resolved
Hide resolved
| ## Limitations | ||
|
|
||
| - Changes to default GUC values for a user or database (ALTER ROLE SET/ALTER DATABASE SET queries) may reflect in other pre-existing active sessions. | ||
| - Connection Manager can only support upto a total of 10,000 pools to route. This includes pools corresponding to dropped users and databases as well. |
There was a problem hiding this comment.
is this simultaneous, or what exactly?
There was a problem hiding this comment.
not simultaneous - Connection Manager can route upto 10,000 unique connection pools over its lifetime as a process. As of now, there is no capability to "clean up" the history of pools for "dead" routes corresponding to users or databases that do not exist
docs/content/stable/explore/going-beyond-sql/connection-mgr-ysql.md
Outdated
Show resolved
Hide resolved
docs/content/stable/explore/going-beyond-sql/connection-mgr-ysql.md
Outdated
Show resolved
Hide resolved
| - Prepared statements may be visible to other sessions within the same connection pool. [#24652](https://github.com/yugabyte/yugabyte-db/issues/24652) | ||
| - Attempting to use DEALLOCATE/DEALLOCATE ALL queries can result in unexpected behavior. [#24653](https://github.com/yugabyte/yugabyte-db/issues/24653) | ||
| - As of now, Connection Manager does not facilitate custom configurations per pool. All configurations used will apply to every pool that Connection Manager routes through. | ||
| - With connection manager enabled, the backend PID stored using JDBC drivers may not accurate. This does not affect backend-specific functionalities (eg. cancel queries), but this PID should not be used to identify the backend process. |
| - Attempting to use DEALLOCATE/DEALLOCATE ALL queries can result in unexpected behavior. [#24653](https://github.com/yugabyte/yugabyte-db/issues/24653) | ||
| - As of now, Connection Manager does not facilitate custom configurations per pool. All configurations used will apply to every pool that Connection Manager routes through. | ||
| - With connection manager enabled, the backend PID stored using JDBC drivers may not accurate. This does not affect backend-specific functionalities (eg. cancel queries), but this PID should not be used to identify the backend process. | ||
| - `currval` and `nextval` functions do not work by default with connection manager enabled. They can be supported with the help of the `ysql_conn_mgr_sequence_support_mode` flag. |
There was a problem hiding this comment.
| - `currval` and `nextval` functions do not work by default with connection manager enabled. They can be supported with the help of the `ysql_conn_mgr_sequence_support_mode` flag. | |
| - By default, `currval` and `nextval` functions do not work when YSQL Connection Manager is enabled. To support these functions, use the `ysql_conn_mgr_sequence_support_mode` flag. |
There was a problem hiding this comment.
the ysql_conn_mgr_sequence_support_mode is not a boolean flag, I can try to incorporate this comment in a similar fashion
There was a problem hiding this comment.
I changed the suggested text slightly
docs/content/stable/explore/going-beyond-sql/connection-mgr-ysql.md
Outdated
Show resolved
Hide resolved
docs/content/stable/explore/going-beyond-sql/connection-mgr-ysql.md
Outdated
Show resolved
Hide resolved
ddhodge
changed the title
Co-authored-by: Dwight Hodge <[email protected]>
docs/content/stable/explore/going-beyond-sql/connection-mgr-ysql.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Dwight Hodge <[email protected]>
docs/content/stable/explore/going-beyond-sql/connection-mgr-ysql.md
Outdated
Show resolved
Hide resolved
This PR adds the "Limitations" section for v2024.2 docs of YSQL Connection Manager.
@netlify /stable/explore/going-beyond-sql/connection-mgr-ysql/