François Egner

Missing this is an absolute show stopper for most people. As an IT admin myself I can tell you that infrastructures running based on docker are super tedious to handle...

> (8.1.0 → 8.2.0 is when the entire protocol message parsing/serialization was rewritten into pg-protocol.) > > This probably isn’t related to the issue, but note that `Client#connect()` is asynchronous;...

> Hi there, > > I believe this issue might be a duplicate of [#3098](https://github.com/brianc/node-postgres/issues/3098). It seems to cover similar concerns. Very interesting. Using Node 16 also fixes the issue...

@thedadow451 Thank you very much for actually doing the digging and providing the potential fix! I am still wondering why its only a few people having this issue and why...

@thedadow451 I can confirm that your patch fixes the issue. From 50-60ms down to 5ms. Node16 still works fine with the latest version (8.13.1). Node18 brings up bad query times...

I had a look at the code and tried to follow timings. I dont know why but thel query-call of ```js const result = await import_tracing.tracer.startActiveSpan("drizzle.driver.execute", (span) => { span?.setAttributes({...

This is actually a problem with the [pg module](https://node-postgres.com/) I am using as the driver for drizzle. Version `8.1.0` of this module is the last one that results in the...

Turns out there is another fix/workaround: Using Node v16 and the newest node-postgres (8.13.0) runs fine too.

@L-Mario564 I already did. For whoever is interested: https://github.com/brianc/node-postgres/issues/3325 Will close this issue.