/**
* Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.
* SPDX-License-Identifier: Apache-2.0.
*/
#pragma once
#include Displays the settings that control the size and behavior of the connection
* pool associated with a DBProxyTarget
.See Also:
AWS
* API Reference
The maximum size of the connection pool for each target in a target group.
* The value is expressed as a percentage of the max_connections
* setting for the RDS DB instance or Aurora DB cluster used by the target
* group.
The maximum size of the connection pool for each target in a target group.
* The value is expressed as a percentage of the max_connections
* setting for the RDS DB instance or Aurora DB cluster used by the target
* group.
The maximum size of the connection pool for each target in a target group.
* The value is expressed as a percentage of the max_connections
* setting for the RDS DB instance or Aurora DB cluster used by the target
* group.
The maximum size of the connection pool for each target in a target group.
* The value is expressed as a percentage of the max_connections
* setting for the RDS DB instance or Aurora DB cluster used by the target
* group.
Controls how actively the proxy closes idle database connections in the
* connection pool. The value is expressed as a percentage of the
* max_connections
setting for the RDS DB instance or Aurora DB
* cluster used by the target group. With a high value, the proxy leaves a high
* percentage of idle database connections open. A low value causes the proxy to
* close more idle connections and return them to the database.
Controls how actively the proxy closes idle database connections in the
* connection pool. The value is expressed as a percentage of the
* max_connections
setting for the RDS DB instance or Aurora DB
* cluster used by the target group. With a high value, the proxy leaves a high
* percentage of idle database connections open. A low value causes the proxy to
* close more idle connections and return them to the database.
Controls how actively the proxy closes idle database connections in the
* connection pool. The value is expressed as a percentage of the
* max_connections
setting for the RDS DB instance or Aurora DB
* cluster used by the target group. With a high value, the proxy leaves a high
* percentage of idle database connections open. A low value causes the proxy to
* close more idle connections and return them to the database.
Controls how actively the proxy closes idle database connections in the
* connection pool. The value is expressed as a percentage of the
* max_connections
setting for the RDS DB instance or Aurora DB
* cluster used by the target group. With a high value, the proxy leaves a high
* percentage of idle database connections open. A low value causes the proxy to
* close more idle connections and return them to the database.
The number of seconds for a proxy to wait for a connection to become * available in the connection pool. Only applies when the proxy has opened its * maximum number of connections and all connections are busy with client * sessions.
*/ inline int GetConnectionBorrowTimeout() const{ return m_connectionBorrowTimeout; } /** *The number of seconds for a proxy to wait for a connection to become * available in the connection pool. Only applies when the proxy has opened its * maximum number of connections and all connections are busy with client * sessions.
*/ inline bool ConnectionBorrowTimeoutHasBeenSet() const { return m_connectionBorrowTimeoutHasBeenSet; } /** *The number of seconds for a proxy to wait for a connection to become * available in the connection pool. Only applies when the proxy has opened its * maximum number of connections and all connections are busy with client * sessions.
*/ inline void SetConnectionBorrowTimeout(int value) { m_connectionBorrowTimeoutHasBeenSet = true; m_connectionBorrowTimeout = value; } /** *The number of seconds for a proxy to wait for a connection to become * available in the connection pool. Only applies when the proxy has opened its * maximum number of connections and all connections are busy with client * sessions.
*/ inline ConnectionPoolConfigurationInfo& WithConnectionBorrowTimeout(int value) { SetConnectionBorrowTimeout(value); return *this;} /** *Each item in the list represents a class of SQL operations that normally
* cause all later statements in a session using a proxy to be pinned to the same
* underlying database connection. Including an item in the list exempts that class
* of SQL operations from the pinning behavior. This setting is only supported for
* MySQL engine family databases. Currently, the only allowed value is
* EXCLUDE_VARIABLE_SETS
.
Each item in the list represents a class of SQL operations that normally
* cause all later statements in a session using a proxy to be pinned to the same
* underlying database connection. Including an item in the list exempts that class
* of SQL operations from the pinning behavior. This setting is only supported for
* MySQL engine family databases. Currently, the only allowed value is
* EXCLUDE_VARIABLE_SETS
.
Each item in the list represents a class of SQL operations that normally
* cause all later statements in a session using a proxy to be pinned to the same
* underlying database connection. Including an item in the list exempts that class
* of SQL operations from the pinning behavior. This setting is only supported for
* MySQL engine family databases. Currently, the only allowed value is
* EXCLUDE_VARIABLE_SETS
.
Each item in the list represents a class of SQL operations that normally
* cause all later statements in a session using a proxy to be pinned to the same
* underlying database connection. Including an item in the list exempts that class
* of SQL operations from the pinning behavior. This setting is only supported for
* MySQL engine family databases. Currently, the only allowed value is
* EXCLUDE_VARIABLE_SETS
.
Each item in the list represents a class of SQL operations that normally
* cause all later statements in a session using a proxy to be pinned to the same
* underlying database connection. Including an item in the list exempts that class
* of SQL operations from the pinning behavior. This setting is only supported for
* MySQL engine family databases. Currently, the only allowed value is
* EXCLUDE_VARIABLE_SETS
.
Each item in the list represents a class of SQL operations that normally
* cause all later statements in a session using a proxy to be pinned to the same
* underlying database connection. Including an item in the list exempts that class
* of SQL operations from the pinning behavior. This setting is only supported for
* MySQL engine family databases. Currently, the only allowed value is
* EXCLUDE_VARIABLE_SETS
.
Each item in the list represents a class of SQL operations that normally
* cause all later statements in a session using a proxy to be pinned to the same
* underlying database connection. Including an item in the list exempts that class
* of SQL operations from the pinning behavior. This setting is only supported for
* MySQL engine family databases. Currently, the only allowed value is
* EXCLUDE_VARIABLE_SETS
.
Each item in the list represents a class of SQL operations that normally
* cause all later statements in a session using a proxy to be pinned to the same
* underlying database connection. Including an item in the list exempts that class
* of SQL operations from the pinning behavior. This setting is only supported for
* MySQL engine family databases. Currently, the only allowed value is
* EXCLUDE_VARIABLE_SETS
.
Each item in the list represents a class of SQL operations that normally
* cause all later statements in a session using a proxy to be pinned to the same
* underlying database connection. Including an item in the list exempts that class
* of SQL operations from the pinning behavior. This setting is only supported for
* MySQL engine family databases. Currently, the only allowed value is
* EXCLUDE_VARIABLE_SETS
.
One or more SQL statements for the proxy to run when opening each new
* database connection. Typically used with SET
statements to make
* sure that each connection has identical settings such as time zone and character
* set. This setting is empty by default. For multiple statements, use semicolons
* as the separator. You can also include multiple variables in a single
* SET
statement, such as SET x=1, y=2
.
One or more SQL statements for the proxy to run when opening each new
* database connection. Typically used with SET
statements to make
* sure that each connection has identical settings such as time zone and character
* set. This setting is empty by default. For multiple statements, use semicolons
* as the separator. You can also include multiple variables in a single
* SET
statement, such as SET x=1, y=2
.
One or more SQL statements for the proxy to run when opening each new
* database connection. Typically used with SET
statements to make
* sure that each connection has identical settings such as time zone and character
* set. This setting is empty by default. For multiple statements, use semicolons
* as the separator. You can also include multiple variables in a single
* SET
statement, such as SET x=1, y=2
.
One or more SQL statements for the proxy to run when opening each new
* database connection. Typically used with SET
statements to make
* sure that each connection has identical settings such as time zone and character
* set. This setting is empty by default. For multiple statements, use semicolons
* as the separator. You can also include multiple variables in a single
* SET
statement, such as SET x=1, y=2
.
One or more SQL statements for the proxy to run when opening each new
* database connection. Typically used with SET
statements to make
* sure that each connection has identical settings such as time zone and character
* set. This setting is empty by default. For multiple statements, use semicolons
* as the separator. You can also include multiple variables in a single
* SET
statement, such as SET x=1, y=2
.
One or more SQL statements for the proxy to run when opening each new
* database connection. Typically used with SET
statements to make
* sure that each connection has identical settings such as time zone and character
* set. This setting is empty by default. For multiple statements, use semicolons
* as the separator. You can also include multiple variables in a single
* SET
statement, such as SET x=1, y=2
.
One or more SQL statements for the proxy to run when opening each new
* database connection. Typically used with SET
statements to make
* sure that each connection has identical settings such as time zone and character
* set. This setting is empty by default. For multiple statements, use semicolons
* as the separator. You can also include multiple variables in a single
* SET
statement, such as SET x=1, y=2
.
One or more SQL statements for the proxy to run when opening each new
* database connection. Typically used with SET
statements to make
* sure that each connection has identical settings such as time zone and character
* set. This setting is empty by default. For multiple statements, use semicolons
* as the separator. You can also include multiple variables in a single
* SET
statement, such as SET x=1, y=2
.