medium10 pts · first answer countsquery-tuningpostgresql
Bad plan right after a bulk load
A job loads 20 million rows into an empty table and immediately runs a join that picks a nested loop and runs for hours. What is the most likely cause and fix?
A job loads 20 million rows into an empty table and immediately runs a join that picks a nested loop and runs for hours. What is the most likely cause and fix?