On Fri, Jun 5, 2026 at 3:08 PM Ashutosh Bapat
<ashutosh.bapat.oss@gmail.com> wrote:
>
> On Fri, Jun 5, 2026 at 1:05 PM Peter Eisentraut <peter@eisentraut.org> wrote:
> >
> > On 02.06.26 13:02, Ashutosh Bapat wrote:
> > > Yes, fix is at the right place. We can not set the varlevelsup to the
> > > correct value in replace_properties_references itself because when
> > > that function is called, we do not know whether UNION is required or
> > > not. The next place to adjust varlevelsup is when creating a UNION
> > > statement.
> > >
> > > Depending upon the varno of outer reference we will see different
> > > symptoms. a crash or an error "plan should not reference subplan's
> > > variable" or even data type mismatch. Also the levelsup is maintained
> > > in nodes other than Var. I have modified the commit message to focus
> > > on the problem instead of the symptom. Also some small edits to the
> > > comments.
> > >
> > > Attached patch has the number 0010 (vs 0001) since I am creating
> > > patches for all the SQL/PGQ fixes from the same branch. It can be
> > > applied independent of other patches.
> >
> > committed
>
> Thanks a lot.
Moving this to the resolved section.
--
Best Wishes,
Ashutosh Bapat
