Brian C

@EdenAzulay > I'm having the same issue when using version 8.3.3 . > Do you know if there are any recent changes on the last releases that might cause the...

Yah looking at this....I think the dns lookup in JS was done before I rewrote libpq bindings and made a proper background async connection worker thread. So this isn't needed...

I'll try rerunning it - very weird error there I didn't on my branches or on [master](https://github.com/brianc/node-postgres/actions/runs/2302982047)

It looks like the errors in CI might be related to this PR...the other PR's I've rebased have all passed CI okay. 😢

I apprecaite the contribution here. You're right, throwing errors on a method that accepts a callback or returns a promise is not a nice pattern. I will be happy to...

yes i am sorry - you're absolutely right this should be merged, and I will do that now & get a new release out tomorrow. There's some epic storm in...

As a workaround you could 'wrap' your arrays in an object and turn that into the JSONB text you want: ``` class JsonBArrayParam { constructor(actualArray) { this.actualArray = actualArray }...

see here: https://github.com/brianc/node-postgres/blob/master/packages/pg/lib/utils.js#L80

Hey @benny-medflyt - thanks for this! Would it be possible to write a test to cover this? Also, if you rebase on master the existing tests should run on this...

> Hi, > When are you guys planning to merge this? There's some code in the original issue. I can use that to write a test & fix. I'll add...