Hacker News new | past | comments | ask | show | jobs | submit login

I'm surprised there was no mention of "query planner" in the article. That would be the first thing I would check instead of assuming the driver had a bug.



A database performance issue was ruled out earlier in the process:

> Node 17 and below worked, Node 18 and above didn’t.

Given that the same queries worked fine with a different client, that would point to a client issue rather than a server issue.


If it was the query planner than I suppose the protocol wouldn't have been the way to make it fail


Sometimes when you think you only changed one variable during a time span, multiple variables may have changed.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: