-
Notifications
You must be signed in to change notification settings - Fork 4.1k
pgwire: consider pprof labeling per-client goroutines #73538
Copy link
Copy link
Closed
Labels
A-sql-executorSQL txn logicSQL txn logicA-sql-pgwirepgwire protocol issues.pgwire protocol issues.C-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)T-sql-foundationsSQL Foundations Team (formerly SQL Schema + SQL Sessions)SQL Foundations Team (formerly SQL Schema + SQL Sessions)
Description
This is a placeholder pending further digging by someone better acquainted with the pgwire code and where we spawn new goroutines, but over in #71622 there was a suggestion that we could apply pprof labels to conn the per-client goroutines with the session ID or other useful identifying info.
Jira issue: CRDB-11628
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
A-sql-executorSQL txn logicSQL txn logicA-sql-pgwirepgwire protocol issues.pgwire protocol issues.C-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)T-sql-foundationsSQL Foundations Team (formerly SQL Schema + SQL Sessions)SQL Foundations Team (formerly SQL Schema + SQL Sessions)