Jack Christensen

`LoadType` is more for user defined types than built in types. Try pgx as of 42d327f660c3e455e0e6668d9c269506bd586188. It doesn't support the binary format, but it should be enough to get it...

The [Path type](https://pkg.go.dev/github.com/jackc/pgx/v5/pgtype#Path) maps to the [PostgreSQL geometry path type](https://www.postgresql.org/docs/current/datatype-geometric.html#DATATYPE-GEOMETRIC-PATHS) not the jsonpath type. At the moment pgx treats jsonpath as text. It doesn't handle the binary representation. To handle...

* The binary format can be used - helpful for UUID, doesn't really matter for jsonpath * Can override the default value returned by `Values()` - instead of `string` you...

pgx uses the binary format for most types it understands including UUID. pgx also supports sql.Scanner for scanned values. However, almost all sql.Scanners will be expecting the text formatted, not...

> But I would assume there could be some saved overhead by passing binary-encoded jsonpaths to Postgres and skipping its parsing overhead. The binary format for input is the same...

I think that will work.

I believe that should work. But you would need a runnable example for anyone else to see exactly what it happening.

You also need to register any composite types. See TestCompositeCodecTranscodeStruct in the pgx source for an example.

Are you sure this is showing current memory usage? I think it is actually showing you total allocations. As in, this isn't a leak, it is a lot of allocations...