Jack Christensen

@jacobmikesell The problem only occurred in very specific circumstances. If the size of the statement cache is exceeded then a query is evicted from the cache, but it is only...

@jacobmikesell I expect a new patch release next week.

@jacobmikesell The fix was included into v5.5.5.

@vytskalt > run the code two times to get this error: You mentioned that you are running on AWS Lambda. It runs fine locally, as would be expected. It's impossible...

> There might be a way to disable prepared statements using pgx but I haven't thoroughly looked into the config settings. Any `ConnConfig.DefaultQueryExecMode` other than the default `QueryExecModeCacheStatement`.

@reVrost I've never used Supabase, so I can't really give any advice there. But `QueryExecModeCacheDescribe` is a good choice *if* you do not have schema changes occurring while your application...

@evanlurvey Can you provide example code demonstrating this?

@evanlurvey Thanks for the clear reproduction. Should be fixed in fd0c65478e18be837b77c7ef24d7220f50540d49.

You can pass Go arrays directly as query arguments. For scanning you need to use `pgtype.Map.SQLScanner`. ```go package main import ( "database/sql" "log" "os" "github.com/jackc/pgx/v5/pgtype" _ "github.com/jackc/pgx/v5/stdlib" ) func main()...

> Do you have any plans to avoid using SQLScanner in future? It makes the data model layer not interoperable if different SQL drivers are in place. pgx supports `[]T`...