Nestjs-Learning fix(deps): update dependency pg to v8

fix(deps): update dependency pg to v8

Open renovate[bot] opened this issue 4 years ago • 0 comments

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
pg	`^7.4.3` -> `^8.0.0`

Release Notes

brianc/node-postgres

Add optional config to pool to allow process to exit if pool is idle.

`v8.6.0`

Compare Source

Better SASL error messages & more validation on bad configuration.
Export DatabaseError.
Add ParameterDescription support to protocol parsing.
Fix typescript typedefs with --isolatedModules.

`v8.5.1`

Compare Source

`v8.5.0`

Compare Source

Fix bug forwarding ssl key.
Convert pg-query-stream internals to typescript.
Performance improvements.

`v8.4.2`

Compare Source

`v8.4.1`

Compare Source

`v8.4.0`

Compare Source

Switch to optional peer dependencies & remove semver package which has been a small thorn in the side of a few users.
Export DatabaseError from pg-protocol.
Add support for sslmode in the connection string.

`v8.3.3`

Compare Source

`v8.3.2`

Compare Source

`v8.3.0`

Compare Source

Support passing a string of command line options flags via the { options: string } field on client/pool config.

`v8.2.2`

Compare Source

`v8.2.1`

Compare Source

`v8.2.0`

Compare Source

Switch internal protocol parser & serializer to pg-protocol. The change is backwards compatible but results in a significant performance improvement across the board, with some queries as much as 50% faster. This is the first work to land in an on-going performance improvment initiative I'm working on. Stay tuned as things are set to get much faster still! :rocket:

`v8.1.0`

Compare Source

Switch to using monorepo version of pg-connection-string. This includes better support for SSL argument parsing from connection strings and ensures continuity of support.
Add &ssl=no-verify option to connection string and PGSSLMODE=no-verify environment variable support for the pure JS driver. This is equivalent of passing { ssl: { rejectUnauthorized: false } } to the client/pool constructor. The advantage of having support in connection strings and environment variables is it can be "externally" configured via environment variables and CLI arguments much more easily, and should remove the need to directly edit any application code for the SSL default changes in 8.0. This should make using [email protected] significantly less difficult on environments like Heroku for example.

`v8.0.3`

Compare Source

`v8.0.2`

Compare Source

`v8.0.1`

Compare Source

`v8.0.0`

Compare Source

note: for detailed release notes please check here

Remove versions of node older than 6 lts from the test matrix. pg>=8.0 may still work on older versions but it is no longer officially supported.
Change default behavior when not specifying rejectUnauthorized with the SSL connection parameters. Previously we defaulted to rejectUnauthorized: false when it was not specifically included. We now default to rejectUnauthorized: true. Manually specify { ssl: { rejectUnauthorized: false } } for old behavior.
Change default database when not specified to use the user config option if available. Previously process.env.USER was used.
Change pg.Pool and pg.Query to be an es6 class.
Make pg.native non enumerable.
notice messages are no longer instances of Error.
Passwords no longer show up when instances of clients or pools are logged.

`v7.18.2`

Compare Source

`v7.18.1`

Compare Source

`v7.18.0`

Compare Source

This will likely be the last minor release before [email protected].
This version contains a few bug fixes and adds a deprecation warning for a pending change in 8.0 which will flip the default behavior over SSL from rejectUnauthorized from false to true making things more secure in the general use case.

`v7.17.1`

Compare Source

`v7.17.0`

Compare Source

Add support for idle_in_transaction_session_timeout option.

`v7.16.1`

Compare Source

`v7.16.0`

Compare Source

Add optional, opt-in behavior to test new, faster query pipeline. This is experimental, and not documented yet. The pipeline changes will grow significantly after the 8.0 release.