Re: SQL Property Graph Queries (SQL/PGQ)

From: Henson Choi <assam258(at)gmail(dot)com>
To: Huanbing Lu <luhuanbing(at)outlook(dot)com>
Cc: Junwang Zhao <zhjwpku(at)gmail(dot)com>, Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Amit Langote <amitlangote09(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-01-11 10:53:44
Message-ID: CAAAe_zCOjyYfEfuyNL1uNBAyXOcYBacFvyJ+cRTLDy4yKjc8Ng@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Huanbing,

Thank you for your interest and insightful question about the
TraversalState
concept. You've identified exactly the right challenge with the custom
executor approach.

However, as Ashutosh suggested, let's keep this thread focused on the
current PGQ patch. Your question about DFS backtracking and PlanState
management deserves a thorough discussion, which we can have once the
current work is committed.

I'm looking forward to discussing VLE implementation details with you
and the community then.

Best regards,
Henson

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 2026-01-11 11:08:46 Re: pgbench - adding pl/pgsql versions of tests
Previous Message Michael Paquier 2026-01-11 10:22:26 Re: IO wait events for COPY FROM/TO PROGRAM or file