Upgrade to pgx and pgxpool v5

[connorgorman]

Description

Pick up the latest changes to the pgx library

Checklist

• Investigated and inspected CI test results
• Unit test and regression tests added
• Evaluated and added CHANGELOG entry if required
• Determined and documented upgrade steps
• Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.

Testing Performed

CI

[roxbot]

Images are ready for the commit at 141cda2.

To use with deploy scripts, first export MAIN_IMAGE_TAG=3.73.x-649-g141cda2d76.

[openshift-ci]

@connorgorman: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/go-postgres-tests	141cda2	link	true	/test go-postgres-tests
ci/prow/gke-postgres-upgrade-tests	141cda2	link	false	/test gke-postgres-upgrade-tests

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[md2119]

I literally did it in one of my PRs because I need this for my search framework enhancements.

[md2119]

Do we want to upgrade v5 now? Seems like the performance of v5 are inferior to v4. Ref: jackc/pgx#1481

[connorgorman]

@md2119

Do we want to upgrade v5 now? Seems like the performance of v5 are inferior to v4. Ref: https://github.com/jackc/pgx/issues/1481

This was on a windows machine. There is an issue resolving arrays which we need to fix. Haven't figured it out yet

[connorgorman]

I'm also tempted to just hide this underneath a struct so it's not a 405 line change

[janisz]

Refs:

• WIP: chore(deps): upgrade pgx to v5 #6915