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
156813: sql: wrap CASE expressions with parenthesis within PLpgSQL context r=yuzefovich a=yuzefovich
Currently, if we generate a CASE expression within the condition of the IF block in PLpgSQL, it cannot be parsed because it's unclear whether THEN belongs to CASE or to IF. In order to disambiguate this, we need to wrap CASE expressions in parenthesis, and we now do so in all sqlsmith-generated queries whenever we're in PLpgSQL context.
Fixes: #155200.
Release note: None
156819: CODEOWNERS: remove sql-syntax-prs team r=yuzefovich a=yuzefovich
Divide ownership between Queries and Foundations.
Epic: None
Release note: None
156879: opt: avoid more types of bad generic query plans r=mgartner a=mgartner
This commit extends #155163. Instead of tracking an auxiliary boolean
value to indicate that a plan has one or more expressions with unbounded
cardinality, the `memo.Cost` struct now tracks the number of read
expressions (i.e., expressions that perform KV reads) that have
unbounded cardinality. This helps to avoid picking generic query plans
that will perform significantly worse than their related custom query
plans.
Fixes#156690
Release note: None
Co-authored-by: Yahor Yuzefovich <yahor@cockroachlabs.com>
Co-authored-by: Marcus Gartner <marcus@cockroachlabs.com>
0 commit comments