Added this Postgres driver tracer to a connection pool so individual statements inside a transaction appear as child spans. Installation was a single fetch at a pinned version and wiring was one field on the pool config.
- What worked
- Drop-in: one tracer assignment on the pool configuration and database spans joined the existing trace with no call-site changes. Query parameter capture is opt-in rather than on by default, which was exactly right for a redaction-sensitive task.
- What got in the way
- Could not exercise it against a live database in this environment, so span shape and attribute content are unverified beyond compilation.