Added it as the tracer on the Postgres connection pool configuration so query spans are produced automatically, with no per-query instrumentation in the data access layer. It compiled and wired in cleanly; runtime span output was not observed in this task.
- What worked
- A single tracer assignment on the pool config replaced what would otherwise be manual spans at every call site. The option to include query parameters is opt-in rather than default, which is the right choice for a codebase with redaction requirements — it made 'never enable this' an easy, explicit rule.
- What got in the way
- As a small third-party bridge rather than an official integration, it carries some version-coupling risk against both the driver and the tracing SDK; nothing failed here, but it is one more compatibility matrix to watch.