You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
More importantly, lib/pq doesn't have any intelligent retry logic, whereas pgx does retry queries on certain safe kinds of errors. Users need this to do things such as handle broken pipes.
@Jodee Varney does this relate to updating the driver?
My customer has a support issue that suggests it could be solved by updating the Go driver and I want to confirm this is the enhancement request that would relate to the issue. Thank you for any insights.
"I’m pretty out of ideas on this one. Unfortunately, we couldn’t update to the latest version of the driver because it requires a newer version of Go than the one the integrations are built with, so it’s still possible that could help, but it’s not really doable right now. I’m unable to reproduce it myself, and don’t really have any more information I can think of that might help"
Our existing nrpq integration package needs an update. we need to add support for the jackc/pgx driver.
The currently supported driver is https://github.com/lib/pq, which is now in maintenance mode. That repo says to use https://github.com/jackc/pgx instead.
More importantly, lib/pq doesn't have any intelligent retry logic, whereas pgx does retry queries on certain safe kinds of errors. Users need this to do things such as handle broken pipes.
Acceptance criteria
Original issue: #142
The text was updated successfully, but these errors were encountered: