-
Notifications
You must be signed in to change notification settings - Fork 4.1k
sql: Joining subqueries causes OOM #21165
Copy link
Copy link
Closed
Labels
A-sql-memmonSQL memory monitoringSQL memory monitoringC-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.C-investigationFurther steps needed to qualify. C-label will change.Further steps needed to qualify. C-label will change.O-communityOriginated from the communityOriginated from the communityS-2-temp-unavailabilityTemp crashes or other availability problems. Can be worked around or resolved by restarting.Temp crashes or other availability problems. Can be worked around or resolved by restarting.
Milestone
Description
A query of the form SELECT * FROM (SELECT * FROM table1 WHERE...) JOIN (SELECT * FROM table2 WHERE...) USING (table2_primary_key_columns) LIMIT 1000 causes nodes to run out of memory. (We have more schema details and the exact query in a non-public bug report) It looks like something memory is not being accounted for correctly. (blaming this on the use of a join on two subqueries is just a guess on my part)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
A-sql-memmonSQL memory monitoringSQL memory monitoringC-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.C-investigationFurther steps needed to qualify. C-label will change.Further steps needed to qualify. C-label will change.O-communityOriginated from the communityOriginated from the communityS-2-temp-unavailabilityTemp crashes or other availability problems. Can be worked around or resolved by restarting.Temp crashes or other availability problems. Can be worked around or resolved by restarting.