"node boltzmann" silently exits if postgres is enabled but not available

[chrisdickinson]

tested on node 14

[ceejbot]

Confirmed on node 14.11. With node 12.18, errors as expected:

hello|⇒ node boltzmann.js
Error: connect ECONNREFUSED 127.0.0.1:5432
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1141:16)

Sticking a try/catch and some logging around the pool.connect() says the exit is happening in pg somewhere.

[ceejbot]

Fixed in the latest pg:

hello|⇒ npm install pg@latest
+ pg@8.3.3
hello|⇒ node boltzmann.js
Error: connect ECONNREFUSED 127.0.0.1:5432
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1141:16)
hello|⇒ volta install node@14
success: installed and set node@14.11.0 (with npm@6.14.8) as default
hello|⇒ node boltzmann.js
Error: connect ECONNREFUSED 127.0.0.1:5432
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1145:16)

[ceejbot]

Leaving this open for now because we don't want to upgrade to pg@latest because of problems related to this bug: brianc/node-postgres#1872 . Looking for a way to sponsor a fix.

[ceejbot]

We've sponsored a fix to this problem in pg, upgraded, and have now resolved this problem.

[laurisvan]

@ceejbot Just to double-check - the related issue (brianc/node-postgres#1872) in pg is still open and I just checked it exist in the latest release. Was the root cause of the problem you experienced something different, after all? If it was the same issue, where did the fix land?