From 3bc9c7cf9da03020c8ea58b4dc6b972e3bdd7834 Mon Sep 17 00:00:00 2001 From: Graham Place Date: Mon, 29 Jul 2024 12:21:07 -0700 Subject: [PATCH] Fix minConnectionIdleTimeSec type in README docs --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 74797b5..9622dd5 100644 --- a/README.md +++ b/README.md @@ -163,7 +163,7 @@ You can then use your plugin like this: | manualMaxConnections | `Boolean` | if this parameters is set to true it will query to get the maxConnections values, to maximize performance you should set the `maxConnections` yourself | `false` | | | maxConnections | `Integer` | Max connections of your PostgreSQL, it should be set equal to `max_connections` in your cluster. I highly suggest to set this yourself | `100` | | | strategy | `String` | Name of your chosen strategy for cleaning up "zombie" connections, allowed values `minimum_idle_time` or `ranked` | `minimum_idle_time` | | -| minConnectionIdleTimeSec | `Integer` | The minimum number of seconds that a connection must be idle before the module will recycle it. | `0.5` | | +| minConnectionIdleTimeSec | `Number` | The minimum number of seconds that a connection must be idle before the module will recycle it. | `0.5` | | | maxIdleConnectionsToKill | `Integer` or `null` | The amount of max connection that will get killed. Default is `ALL` | `null` | | | connUtilization | `Number` | The percentage of total connections to use when connecting to your PostgreSQL server. A value of `0.80` would use 80% of your total available connections. | `0.8` | | | debug | `Boolean` | Enable/disable debugging logs. | `false` | |