mirror of
https://github.com/hasura/graphql-engine.git
synced 2024-09-11 10:46:25 +03:00
improve description for retry in pool settings
fixes https://hasurahq.atlassian.net/browse/NDAT-749 PR-URL: https://github.com/hasura/graphql-engine-mono/pull/9706 GitOrigin-RevId: c94d3e152efdef15fe4e973a7aa8904db7468613
This commit is contained in:
parent
5029b67a23
commit
f0a627061f
@ -156,7 +156,7 @@ keywords:
|
||||
| max_connections | false | `Integer` | Maximum number of connections to be kept in the pool (default: 50) |
|
||||
| total_max_connections | false | `Integer` | Maximum number of total connections to be maintained across any number of Hasura Cloud instances (default: 1000). Takes precedence over `max_connections` in Cloud projects. _(Only available in Hasura Cloud)_ |
|
||||
| idle_timeout | false | `Integer` | The idle timeout (in seconds) per connection (default: 180) |
|
||||
| retries | false | `Integer` | Number of retries to perform (default: 1) |
|
||||
| retries | false | `Integer` | Number of retries to perform when failing to acquire connection (default: 1). Note that this configuration does not affect user/statement errors on PG. |
|
||||
| pool_timeout | false | `Integer` | Maximum time to wait while acquiring a Postgres connection from the pool, in seconds (default: forever) |
|
||||
| connection_lifetime | false | `Integer` | Time from connection creation after which the connection should be destroyed and a new one created. A value of 0 indicates we should never destroy an active connection. If 0 is passed, memory from large query results may not be reclaimed. (default: 600 sec) |
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user