Re: SQL Property Graph Queries (SQL/PGQ) - Mailing list pgsql-hackers

From Ashutosh Bapat
Subject Re: SQL Property Graph Queries (SQL/PGQ)
Date
Msg-id CAExHW5vNZqCXuemXVL+nDDYkBeqJXdM3s=M3PWnymL6xqeB2WA@mail.gmail.com
Whole thread
In response to Re: SQL Property Graph Queries (SQL/PGQ)  (Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>)
Responses Re: SQL Property Graph Queries (SQL/PGQ)
List pgsql-hackers
On Thu, Feb 19, 2026 at 3:01 PM Ashutosh Bapat
<ashutosh.bapat.oss@gmail.com> wrote:
>
>
> I am actually wondering whether the comment in parserOpenPropGraph()
> is required. In case we want to keep it, the attached patch has a typo
> fix. It also has some more improvements.
>
> >
> > Also, see this patch:
> >
> > https://www.postgresql.org/message-id/6d3fef19-a420-4e11-8235-8ea534bf2080%40eisentraut.org
> >
> > If this is accepted, it would make the change in the patch here even
> > smaller.
>
> +1. I think we should commit this, rebase SQL/PGQ patches and then
> apply this change.

Thanks for committing those patches. Here's a patchset rebased on top
of these commits.

0001 is the same as earlier 0001, but with a conflict in
pg_overexplain.sql/.out resolved. It needs 0002 so that a property
graph can be used in the GRAPH_TABLE clause.
0002 is your patch to add parserOpenPropGraph() with the typo and
comment fixed as mentioned above. It should be squashed into 0001 in
the next patchset.

--
Best Wishes,
Ashutosh Bapat

Attachment

pgsql-hackers by date:

Previous
From: Richard Guo
Date:
Subject: Re: Consider low startup cost in add_partial_path
Next
From: Kirill Reshke
Date:
Subject: Re: amcheck: fix bug of missing corruption in allequalimage validation