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
Currently we already return selectivity = 1 in this case. This doesn't sound entirely correct. Self join can be observed in many cases, either user query, or subquery unnesting. We will see a distinct scan joined with the original scan on the right side of the dependent join. Ideally, it should directly give back the row count of the scan instead of giving selectivity = 1 (which is row count * row count).
The text was updated successfully, but these errors were encountered:
Currently we already return selectivity = 1 in this case. This doesn't sound entirely correct. Self join can be observed in many cases, either user query, or subquery unnesting. We will see a distinct scan joined with the original scan on the right side of the dependent join. Ideally, it should directly give back the row count of the scan instead of giving selectivity = 1 (which is row count * row count).
The text was updated successfully, but these errors were encountered: