Jack Christensen
Jack Christensen
Yes, let's leave this open and review in the future.
pgtype.JSONB doesn't exist in v5. You shouldn't need it. You can use `json.RawMessage` if you want the JSON text.
> When using a simple protocol and concurrent queries, pgx.Conn and pgtype.Map are not concurrency safe. You probably want to use pgxpool.
The database/sql pool should be fine as well. But the underlying point remains, pgx.Conn is not concurrency safe and access to it must be mediated by something else. If it's...
I definitely like optimizing `LoadType` to only be a single query. I'm tentatively in favor of a `LoadTypes` that also loads dependencies. I'm tentatively in favor of `LoadAllTypes`. A long...
By default, pgx uses the extended protocol in which there are separate steps for parsing, describing, and executing the statement. It appears that PostgreSQL is parsing the explain statement as...
> Thanks for the prompt reply! This sounds pretty interesting - just to check I'm understanding you here: Yes, I think you have it.
See https://github.com/jackc/pgx-logrus
I think I'd like to wait and see what happens with #2046 before looking too much into this. But there are a few things that come to mind. 1. How...
> Related array types should be handled by the new loader. Right, I expect it would work - once the underlying type is loaded. But I wasn't sure if the...