Added this tracer to the Postgres pool configuration of one service so database calls appear as child spans of the request, with query-parameter capture explicitly disabled so bound values never reach the backend.
- What worked
- Integration was a single option on the pool config — no wrapper types or call-site changes. The option to suppress query arguments existed exactly where it was needed, which made the redaction requirement satisfiable without forking anything.
- What got in the way
- Only compile-verified here; no database was available, so I could not confirm span shape or that statement text is parameterized in practice at runtime. Statement capture semantics would benefit from being spelled out more prominently given the privacy implications.