Jack Christensen
Jack Christensen
I took a fresh look at this, and I wonder if `time.AfterFunc` would be a simpler solution. Instead of `triggerHealthCheck` starting a goroutine and sleeping, the whole `triggerHealthCheck` call could...
> Note that I needed to introduce a mutex for synchronization over the new timer field. I considered instead just setting this field up as part of pool init so...
Do I understand correctly that this is to save a type cast or is it doing more? Without tests its a bit hard to follow the intent.
As far as I can tell you can do the same by assigning the result of `CollectRows` with `=` to a variable of your desired type rather than using `:=`...
> Would it be possible to, one way or another, allow Type to be serialised? Yes, but it seems rather error prone. I'm more inclined to improve performance of loading...
Your full example is fairly long, so I didn't debug it. But I did add a working test to the pgx test suite that shows the tracer executing in a...
There's nothing that someone else can try to run here. > You'll see something like this in the generated code What do you mean generated code? pgtype doesn't have any...
Using pgx directly should have better performance than using database/sql. The pgx database/sql driver is implemented on top of the native pgx interface so in theory it should always be...
Here are some things you could try in rough order of difficulty: 1. Cast the timestamp to string in your query (e.g. `SELECT created_at::text FROM table`). 2. Tell pgx to...