Add support for v5 of the pgx Go driver

[kyleconroy]

What do you want to change?

This proposal is a work in progress

v5.0.0 of jackc/pgx is coming in September (jackc/pgx#1273). The changes are significant. I think it's a good opportunity to make some backwards-incompatible changes to fix some long standing issues with our pgx support

What issues should be fixed?

• Postgresql 2D array in database schema generated as 1D array in models.go #1494
• Running :copyfrom with a uuid causes ERROR: incorrect binary data format (SQLSTATE 22P03) with PGX #1507
• Column override with query alias produces wrong type #1752
• Add type support for pgtype.Point #1641
• feat: add support for Postgres multi dimensional arrays in Go #1651
• Fix postgresql time #1623

What database engines need to be changed?

PostgreSQL

What programming language backends need to be changed?

Go

[mcdoker18]

Hi @kyleconroy !

I decided to try to implement the support pgx v5 in the sqlc. I should have discussed the implementation details with you before I started to work. Sorry for this. But It doesn't take too much time, so I opened 3 PRs:

• [PART 1] pgx v5 support (#1823) #1873 - To support two version of pgx in the e2e tests at the same time we move 'pgx/v4' tests to the separated v4 directory. Then new 'pgx/v5' e2e tests will be located in the v5 dir.
• [PART 2] pgx v5 support (#1823) #1874 - support pgx v5 in the sqlc
• [PART 3] pgx v5 support (#1823) #1875 - added e2e tests for pgx v5

[kyleconroy]

@mcdoker18 wow, thank you! I'm a bit short on time right now, so please excuse the slow review times. I'm hoping to get these reviewed within the next week.

[advdv]

Looking forward to this!

[brlala]

hopefully this gets merged