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. #doordashfairy 1,141 posts
- 2. Vanity Fair 65.4K posts
- 3. Susie Wiles 131K posts
- 4. Mustapha Kharbouch 28.5K posts
- 5. Mick Foley 34.3K posts
- 6. Olive Garden 1,285 posts
- 7. Larian 11.8K posts
- 8. Mary and Joseph 1,943 posts
- 9. Brookline 10.3K posts
- 10. Snowslingers N/A
- 11. Christensen 5,487 posts
- 12. Michelea Ponce 35.7K posts
- 13. Penguins Christmas Party Time N/A
- 14. $TSLA 50.8K posts
- 15. Firefox 5,705 posts
- 16. Cardiff 28.5K posts
- 17. Brand New Day 10.5K posts
- 18. Kay Flock 1,355 posts
- 19. Carville 3,616 posts
- 20. Gittens 7,851 posts
Loading...
Something went wrong.
Something went wrong.