Document pgx driver latency caveat with full DBM propagation mode - #38534
Draft
pierreln-dd wants to merge 1 commit into
Draft
Document pgx driver latency caveat with full DBM propagation mode#38534pierreln-dd wants to merge 1 commit into
pierreln-dd wants to merge 1 commit into
Conversation
Add a callout to the Go tab of Connect DBM and APM warning that enabling full propagation mode with the pgx driver can force statement re-planning and increase query latency, since pgx caches prepared statements by query text and full mode injects unique trace context per query. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Contributor
Preview links (active after the
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do? What is the motivation?
Adds a callout to the Go tab of Connect DBM and APM warning about a latency regression when using the
pgxdriver withfullpropagation mode.pgxcaches prepared statements by query text. Becausefullmode injects unique trace context into each query, it defeats this cache and forces the database to re-plan every query. Recommendsservicemode as a workaround.Merge instructions
Merge readiness:
Additional notes