You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
select: don't replace EQ/REQ by GE/LE in planner with after
Before the patch we copy an original EQ/REQ condition to post-filter
and change the original to GE/LE. The problem is that EQ/REQ can't be
a stop condition. As a result EQ/REQ + after unexpectedly became a
full scan.
The patch removes this behavior, the query becomes more expected and
in base executes as regular EQ/REQ.
We had an idea to replace EQ with GE+LE. This would help to skip less
tuples in the executor inside scroll_to_after_tuple. But unfortunately,
due to a bug[1], this will break the current behavior. So we need to
fix the bug first.
In additional, the 'potentially long select'[2] warning is confused by
the GE/LE in the query plan.
This patch only changes the internal behavior and does not affect a
client code.
1. #301
2. #277
0 commit comments