Too Many Hash Joins in Postgres Will Consume Disastrous Disk Volume
Published:
It seems that 200GB storage aren’t enough for a terrible query plan. If we use too many Hash Joins in a complicated SQL(like those in Join Order Benchmark), there will be a spike in the disk usage and if it exceeds the ceiling, well then the process will crash :(
So maybe I need to set a monitor on the disk usage, once it will exceed the ceiling with a high probabilty, just cancel this query plan and mark a special sign there in the Weight & Bias log.
I’m glad I’m not the person who will pay the bill:)
“Almost 30-40 dollars vanished”
“Crashes in Weights & Bias”