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. #Survivor49 13.7K posts
- 2. Disturbed 6,600 posts
- 3. #PresidentialAddress 15K posts
- 4. Savannah 17K posts
- 5. Newt 2,200 posts
- 6. Cartoon Network 1,613 posts
- 7. Kristina 4,452 posts
- 8. Garfunkel N/A
- 9. IT MATTERS 48.9K posts
- 10. Jake Allen N/A
- 11. #AEWDynamite 23.4K posts
- 12. Rizo 2,157 posts
- 13. Jimmy Fallon 5,710 posts
- 14. Cavs 7,671 posts
- 15. Warrior Dividend 28.9K posts
- 16. Billie Eilish 11.4K posts
- 17. #SistasOnBET 2,558 posts
- 18. Bernie Mac N/A
- 19. Delaware 6,212 posts
- 20. Adderall 5,601 posts
Loading...
Something went wrong.
Something went wrong.