Vitaly Tomilov

You are not the first one to make that mistake, and I just updated the documentation to underline this. From https://github.com/vitaly-t/pg-promise#connection > Object db represents the database protocol, with lazy...

> A great example of this is node's use of callbacks. Early on node experimented with a feature called 'promises' that added a number of features to make async code...

A typical `ON CONFLICT` clause is static, which means it can be simply appended to the generated query. And this is how it is done within pg-promise, b.t.w.

You already have several approaches to diagnosing errors - `error` event, `pg-monitor`, and Bluebird long-stack tracing. Using at least one of them is sufficient.

> the error event doesn't have context information in the stack Bluebird stack has all the details. > pg-monitor needs to be attached to log queries, which will usually occur...

Added [a memo](https://github.com/vitaly-t/pg-promise/issues/355) to help with a possible upgrade.

@dmfay one of the recommended improvements - reuse of the pg-promise configuration for the custom promise library when using its `db` object. `db` object gives you access to the generic...

> I've been trying to do something weird with proxies for the connection pools -- mixed results so far :) Are you talking about the use of `pg-promise` version 6.x?

The latest pg-promise version is 6.0.26. Within pg-promise architecture you get a new pool with each new `db` object you create by calling `db = pgp(connection)`. The idea is to...

[pg-promise 6.x has been officially released](https://github.com/vitaly-t/pg-promise/releases/tag/v.6.1.0).