Re: SQL Property Graph Queries (SQL/PGQ)

From: Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>
To: Alexander Lakhin <exclusion(at)gmail(dot)com>
Cc: Peter Eisentraut <peter(at)eisentraut(dot)org>, assam258(at)gmail(dot)com, Amit Langote <amitlangote09(at)gmail(dot)com>, Junwang Zhao <zhjwpku(at)gmail(dot)com>, Vik Fearing <vik(at)postgresfriends(dot)org>, Ajay Pal <ajay(dot)pal(dot)k(at)gmail(dot)com>, Imran Zaheer <imran(dot)zhir(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: SQL Property Graph Queries (SQL/PGQ)
Date: 2026-05-16 12:12:20
Message-ID: CAExHW5t8uobr+WjEON72cOpseOG2Wh7pSzWpn9Hq3DkLopu4Fg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Alexander,

On Sat, May 16, 2026 at 5:30 PM Alexander Lakhin <exclusion(at)gmail(dot)com> wrote:
>
> Hello hackers,
>
> Please look at an internal error produced with the following script added
> to src/test/regress/sql/graph_table.sql:
> CREATE TABLE x(a int);
> SELECT * FROM x, GRAPH_TABLE (myshop MATCH (c IS customers) ->(l IS orders | wishlists) COLUMNS (c.name, x.a AS a));
>
> ERROR: XX000: plan should not reference subplan's variable
> LOCATION: finalize_plan, subselect.c:3159

Thanks for the report. It will be better to start a new thread for
SQL/PGQ issues so that they can be tracked in open items if required.

I am wondering if this issue is related to the issue reported at [1]
and has the same root cause.

[1] https://www.postgresql.org/message-id/CAHg+QDfnLzsgjaQ_CiKSpP4JH3MKOiwoawEcCzXa9uYr45yiWw@mail.gmail.com

--
Best Wishes,
Ashutosh Bapat

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Lakhin 2026-05-16 13:00:00 Re: SQL Property Graph Queries (SQL/PGQ)
Previous Message Andrew Dunstan 2026-05-16 12:00:25 Re: bump minimum supported version of psql and pg_{dump,dumpall,upgrade} to v10