fix(schema): add missing FK indexes and constraints#1776
Conversation
BenchstatBase: |
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
8933544 to
72c72bb
Compare
Add 74 missing indexes on foreign key columns across all schema files. PostgreSQL does not auto-create indexes for FK columns, causing full sequential scans on joins, cascade deletes, and filtered queries. Also add two missing FK constraints: - logging_backends.agent_id -> agents.id - external_roles.scraper_id -> config_scrapers.id Reference: https://pi.dev/session/#23fc14d97915172bb47a9799228d080b
72c72bb to
3988d94
Compare
Add 74 missing indexes on foreign key columns across all schema files.
PostgreSQL does not auto-create indexes for FK columns, causing full
sequential scans on joins, cascade deletes, and filtered queries.
Also add two missing FK constraints:
Agent Conversation: https://pi.dev/session/#23fc14d97915172bb47a9799228d080b