Unhandled 'error' event

[forbeslindesay]

Unhandled 'error' event

[ForbesLindesay]

The streaming APIs are very difficult to test. If you can produce a test case showing a problem where I just need a Postgres docker container and a JavaScript file to run, I am happy to look into fixing issues.

[bharatiprashant]

Hi @ForbesLindesay, the problem exists from the DB side my DB cannot take a load and it terminates the connection. it there any way to retry the connection.
For the test case, I need to have millions of data on my table and do a CPU intensive task

also is this the right way to handle the error

const db = createConnectionPool({
  bigIntMode: "bigint",
  user: app.db_user,
  host: app.db_host_reader,
  database: app.db_name,
  password: app.db_password,
  port: app.db_port,
  keepAlive: true,
  poolSize: 5,
  idleTimeoutMilliseconds: 0,
  connectionTimeoutMilliseconds: 0,
  onError(err) {
    console.log(err);
  },
});

[ForbesLindesay]

That onError is only for errors in connections that are in the pool. To handle errors during the stream, you would need to attach an error handler to the node.js stream using .on('error', err => console.log(err))

[ForbesLindesay]

The latest release does fix some errors related to unhandled errors in Postgres connections, so I suspect this may be resolved. If you can still reproduce it, please open a fresh issue with a failing test (it's ok if it's a test that only fails 1% of the time as we can just put it in a for (let i = 0; i < 1000; i++) loop)