pg-promise 10.5.0-beta.1 → 10.5.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +1 -1
- package/package.json +1 -1
- package/typescript/pg-subset.d.ts +7 -3
package/README.md
CHANGED
|
@@ -974,7 +974,7 @@ db.txIf({cnd}, t => {
|
|
|
974
974
|
This library manages all database connections via the [connection pool], which internally caches them.
|
|
975
975
|
|
|
976
976
|
Connections in the cache expire due to inactivity after [idleTimeoutMillis] number of milliseconds, which you
|
|
977
|
-
can set when creating the [Database] object.
|
|
977
|
+
can set only when creating the [Database] object.
|
|
978
978
|
|
|
979
979
|
While there is a single open connection in the pool, the process cannot terminate by itself, only via `process.exit()`.
|
|
980
980
|
If you want the process to finish by itself, without waiting for all connections in the pool to expire, you need
|
package/package.json
CHANGED
|
@@ -212,9 +212,13 @@ declare namespace pg {
|
|
|
212
212
|
// 0 will disable connection pooling
|
|
213
213
|
max: number
|
|
214
214
|
|
|
215
|
-
// max milliseconds a client can go unused before it is removed
|
|
216
|
-
//
|
|
217
|
-
|
|
215
|
+
// max milliseconds a client can go unused before it is removed from the pool and destroyed;
|
|
216
|
+
//
|
|
217
|
+
// Made unavailable in v10.5.0, due to the following:
|
|
218
|
+
// - https://github.com/brianc/node-postgres/issues/2139
|
|
219
|
+
// - https://github.com/vitaly-t/pg-promise/issues/703
|
|
220
|
+
//
|
|
221
|
+
// idleTimeoutMillis: number
|
|
218
222
|
|
|
219
223
|
client_encoding: string
|
|
220
224
|
|