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
We just saw a sentry report where we hit a nil pointer with
`planner.curPlan.instrumentationHelper` being nil when trying to log
a statement. This happened after we hit an error in `handleAOST`, so we
short-circuited "dispatch to execution engine" part, meaning that the
plan is left uninitialized. Previously, in
eac1971 we attempted to handle such
scenarios by tracking a boolean indicating whether the dispatch has
occurred, but in this case we marked the boolean "true" (meaning it has
occurred), yet we short-circuited due to an error.
This commit refactors how we ensure that the plan is initialized by
simply checking whether the corresponding fields are set or not. In
turn, this exposed the fact that we previously didn't unset
`planner.curPlan` when resetting the planner, which is now fixed.
I spent some time trying to come up with a repro but didn't succeed, so
there is no regression test.
Release note: None
0 commit comments