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
The gapfill CustomScan node did not work correctly when used inside a
LATERAL subquery because gapfill_rescan had two bugs:
1. It did not call UpdateChangedParamSet on its child plan state before
ExecReScan, so the child plan did not know that LATERAL parameters
changed and kept returning stale data from the previous outer row.
2. It did not reset internal gapfill state (next_timestamp, next_offset,
groups_initialized, column states) on rescan, so gap-filling was
skipped on subsequent scans since next_timestamp was already at
gapfill_end.
Fixestimescale#4693
0 commit comments