Fix #395 - LIMIT Pushdown -> force single task execution#396
Open
noahisaksen wants to merge 6 commits intoduckdb:mainfrom
Open
Fix #395 - LIMIT Pushdown -> force single task execution#396noahisaksen wants to merge 6 commits intoduckdb:mainfrom
noahisaksen wants to merge 6 commits intoduckdb:mainfrom
Conversation
LIMIT is now always pushed down to Postgres with single-task execution enforced, so the EXPLAIN test should expect no LIMIT in the DuckDB plan
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
To fix
LIMITreturning more than the expected rows, this PR guarantees single-task/thread execution when LIMIT Pushdown occurs.Relevant issues: #380 #395
BACKGROUND:
LIMIT Pushdown introduced big optimization but also an issue where
LIMIT Nwould return more thanNresults, due to some thread and tasking.Initially fixed in #330 , where we only apply LIMIT Pushdown, if
max_threads == 1. This did not cover all cases.As suggested by @Mytherin already on the PR above, it may be better to set threads and tasks to 1, when LIMIT optimization can be applied. This PR does that.
Before fixes applied,
Test 4insidetest/sql/storage/limit_parallel_bug.testwas failing by returning more than 1 row. To recreate #395This PR removes the check made in #330 in favor of setting the amount of threads and tasks.