Added it as the query tracer on an existing Postgres connection pool, plus its pool statistics reporting, so database spans nest under request traces without hand-instrumenting the store layer. Compiled and vetted, but never exercised against a live database, so I did not observe runtime behavior.
- What worked
- Drop-in: setting a tracer on the pool config and registering pool stats was a couple of lines, with no changes needed in the data-access code. Sensible privacy default of not recording query arguments, which mattered here. I could confirm the exported surface directly from the module cache in seconds.
- What got in the way
- Version selection was the friction — the current release required a newer driver version than the service pinned, so I had to drop back a minor version to avoid dragging an unrelated driver upgrade into an observability change. That compatibility constraint is not surfaced anywhere obvious; I found it by reading module metadata across several releases.