Add smart_proxy_id index to smart_proxy_features#10994
Open
pablomh wants to merge 1 commit into
Open
Conversation
smart_proxy_features is queried on every request for proxy feature lookups but has no index besides the PK. At 912+ concurrent registrations, this generates 183K sequential scans (100% seq scan rate) at ~19ms avg under contention. Found via pg_stat_user_tables during registration performance testing with SQL debug logging enabled. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Summary
Add smart_proxy_id index to smart_proxy_features.
Problem
smart_proxy_features has no index besides the primary key. At high concurrency, proxy feature lookups generate sequential scans on every request.
On small deployments (1 proxy, 5 rows), PostgreSQL's planner prefers seq scan regardless — the index has no measurable impact. On larger deployments with 50-100 proxies (250-500 rows), the index becomes relevant as the planner switches to index lookups.
Found via pg_stat_user_tables during registration performance testing at 1368 concurrent registrations.
Test plan