Support MultiQueryTracer
- Dominant language
- Go
- Stars
- 14.3k
- Forks
- 1.1k
- Avg merge
- 6d 9h
- Merged PRs (30d)
- 11
Description
**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
By using the `MultiQueryTracer` proposed in the following PR, I was able to set tracer and logger respectively.
I thought this is a case that other people might need.
- https://github.com/jackc/pgx/issues/1061
Do you plan to incorporate this into the pgx itself?
**Describe the solution you'd like**
A clear and concise description of what you want to happen.
I'd be happy to see it implemented in the pgx itself.
**Appendix**
- https://github.com/jackc/pgx/discussions/1677
Contributor guide
Research direction
Start by reading the proposed MultiQueryTracer PR in issue #1061 and the related discussion in #1677, then examine how pgx currently handles tracers and loggers. Done means agreeing on and implementing native support for separately configured tracing and logging in pgx.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, postgresql
- Domain
- backend-api-design, observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100