Re: SQL/PGQ: quantified path patterns unsupported in GRAPH_TABLE (19beta2/beta3) — known gap or on the roadmap?

From: Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>
To: chris(at)chrisleephd(dot)us
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: SQL/PGQ: quantified path patterns unsupported in GRAPH_TABLE (19beta2/beta3) — known gap or on the roadmap?
Date: 2026-09-02 04:13:48
Message-ID: CAExHW5uFo+2x8bcBWRMMeX9S+0OkY6EBQ_8-f5+L=kh=ufwTzQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Sep 1, 2026 at 11:38 PM chris <chris(at)chrisleephd(dot)us> wrote:

>
> A few questions, if anyone can point me in the right direction:
>
> 1. Is quantified path pattern support intentionally deferred past 19, or is there a patch/commitfest entry already in flight that I should be watching?

It's deferred. There is no concrete proposal (which covers all aspects
of quantified path) with patch yet.

> 2. If it's deferred, is there a tracking thread or open item I could link to, so the book can point readers at the right place instead of just saying "not yet"?

none ATM

> 3. Is there a recommended workaround inside SQL/PGQ itself for unbounded-depth traversal, or is a recursive CTE still the correct answer for that case in 19?
>

recursive CTE

> Thanks for all the work getting SQL/PGQ this far — the fixed-depth pattern matching and undirected edge support are genuinely nice additions.
>

Thanks for the compliments.

--
Best Wishes,
Ashutosh Bapat

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bertrand Drouvot 2026-09-02 04:34:19 Re: pgstat: Flush some statistics within running transactions, take 2
Previous Message Amit Kapila 2026-09-02 04:03:39 Re: Logical replication row filter loses unchanged toasted columns