Vadim

seems like pgx v5 got released: https://github.com/jackc/pgx/releases/tag/v5.0.0

it looks like `github.com/jackc/pgtype` should be replaced with `github.com/jackc/pgx/v5/pgtype` according to https://github.com/jackc/pgx/blob/f803c790d0999e9028cbffefad9df02e4aff913a/CHANGELOG.md#merged-packages, so I just submitted https://github.com/georgysavva/scany/pull/97

pgx v5 finally added tracing capabilities - https://github.com/jackc/pgx/blob/master/tracer.go, so it should be now possible to implement this integration

I also experience a similar behavior in docker containers with SQL client (.net 5, dd-trace-dotnet 1.22.0). Is there a way to figure out/measure the overhead of datadog tracing?

@colin-higgins yes, I'm on version `1.27.0` and the first request is still slow.

@pierotibou we've moved to version 2.1.0 of the tracer. It seems like it works just a bit faster: 

I tried to do it through `make install` as well. It works only when add `-lws2_32` to CGO_LDFLAGS in `script/with-static.sh` and add `-G"MinGW Makefiles"` option to cmake in `build-libgit2-static.sh` (otherwise...

@clns I tried the same things and couldn't get it working. So I ended up compiling `libgit2` to a separate dll and used dynamic linking instead of static one. I...

Try to put `libgit2.dll` side by side with your executable or somewhere in your `%PATH%`.

unfortunately it does not, the error log I'm getting looks like this: ``` proxy | 2024/01/25 21:15:05 [124] GET https://xyz.jfrog.io:443/artifactory/api/nuget/nuget-local/Download/MyPackage/1.2.0 proxy | 2024/01/25 21:15:05 [124] 403 https://xyz.jfrog.io:443/artifactory/api/nuget/nuget-local/Download/MyPackage/1.2.0 proxy | 2024/01/25...