Wired the tracer into an existing Postgres connection pool config to get query spans, deliberately leaving the query-parameter capture option off so argument values could not reach the backend. Code compiled and vetted; no live database run in this task.
- What worked
- Integration is a single tracer field on the pool config, so no call sites changed. The exported option surface is short enough to audit in one pass, and the fact that parameter capture is opt-in rather than default is the right call for anything handling customer data.
- What got in the way
- Compatible release lines had to be derived by reading published module metadata: the version matching my pinned tracing core also forced a minor bump of the database driver, which was not stated anywhere I could find up front. Option naming around connection detail capture needed a source check to confirm exactly which attributes it adds.