Skip to content

db: add composite indexes for telemetry query performance #381

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
codewithzubair07 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

db: add composite indexes for telemetry query performance #381

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 28 additions & 0 deletions src/database/migrations/001_telemetry_query_indexes_rollback.sql
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
Closes #347

## Problem
Analytical dashboard queries bog down when scanning unindexed columns
in large telemetry tables, especially for deep historical metrics.

## Solution
Added composite index migration files in `src/database/migrations/`:

### Files added
- `001_telemetry_query_indexes.sql` — 10 composite indexes across 6 tables
- `001_telemetry_query_indexes_rollback.sql` — rollback script

### Indexes added
| Table | Index | Query accelerated |
|---|---|---|
| `PriceHistory` | `source, timestamp` | Provider history over time |
| `PriceHistory` | `currency, source, timestamp` | Dashboard per-pair per-provider |
| `OnChainPrice` | `currency, ledgerSeq` | Ledger history pagination |
| `OnChainPrice` | `currency, confirmedAt` | Time-range dashboard queries |
| `RawData` | `provider, currency, fetchedAt` | Validator/provider telemetry |
| `OhlcCandle` | `currency, granularity, openTime` + INCLUDE | Sparkline charts |
| `ErrorLog` | `providerName, occurredAt` | Recent errors per validator |
| `ProviderReputation` | `status, reliabilityScore` | Validator ranking |
| `ProviderReputation` | `providerName, lastUpdated` | Staleness monitoring |
| `ComplianceMetadata` | `eventType, resolved, createdAt` | Latency violation dashboard |

All indexes use `CONCURRENTLY` to avoid table locks in production.
Loading