Re: (SQL/PGQ) cache lookup failed for label

Hi Ashutosh,

On Thu, Jun 4, 2026 at 7:46 PM Ashutosh Bapat
<ashutosh(dot)bapat(dot)oss(at)gmail(dot)com> wrote:
>
> Hi Ewan,
>
> On Thu, Jun 4, 2026 at 4:52 PM Ewan Young <kdbase(dot)hack(at)gmail(dot)com> wrote:
> >
> >
> > I don't think these are the same bug. I applied v20260601-0005
> > through 0007 on top of master (90354030b8f) and my test case still
> > fails the same way:
>
> Sorry to redirect you to the wrong thread. Please check [1]. Hope I
> have given you the right one this time :)
>
> When submitting the next report, please check if the issue is already
> covered by an existing email thread.
>
> [1] https://www.postgresql.org/message-id/CAHg+QDfnLzsgjaQ_CiKSpP4JH3MKOiwoawEcCzXa9uYr45yiWw@mail.gmail.com

No problem, and thanks for the pointer — this time it is indeed the
same issue. I applied v20260602-0010 on top of master (90354030b8f)
and verified that it fixes my test case as well as an edge-label
variant of it; the graph_table regression test also passes. The fix
is essentially the same as the one I posted (adjusting varlevelsup of
the path queries when they get wrapped as subqueries of the UNION),
just placed in generate_setop_from_pathqueries instead, which also
looks cleaner to me. So please consider my report a duplicate of that
thread.

I will dig the archives more carefully before reporting next time :)

Regards,
Ewan Young

>
> --
> Best Wishes,
> Ashutosh Bapat