Ran into this on my benchmark data set! Canceled a query that had already run for two days, found this plan: Nested Loop (cost=78,613,867,046.43 rows=20,718,100 width=1144) Oopsie! Add missing index, 6 minutes: Nested Loop (cost= 1,881,853,963.95 rows=495,950 width=1144)
Postgres performance best practice: index all foreign keys. Primary keys are automatically indexed but if you reference a primary key in another table using a foreign key, that is not automatically indexed - and an index needs to be added manually.
United States เทรนด์
- 1. The JUP 441K posts
- 2. Greg Biffle 11K posts
- 3. FINALLY DID IT 443K posts
- 4. Hunger Games 6,735 posts
- 5. Statesville 10.8K posts
- 6. NextNRG 2,718 posts
- 7. Cleetus N/A
- 8. Jason Kidd 1,504 posts
- 9. Kennedy Center 3,827 posts
- 10. Helene 6,581 posts
- 11. #DareYouToDeathEP1 1.16M posts
- 12. #thursdayvibes 3,668 posts
- 13. #NicolandriaxGlamour 11.5K posts
- 14. Zollers N/A
- 15. Skenes 4,473 posts
- 16. Pribula 1,006 posts
- 17. Inflation 158K posts
- 18. Kerry Kittles N/A
- 19. Team USA 7,434 posts
- 20. Vince Carter N/A
Loading...
Something went wrong.
Something went wrong.