Re: SQL Property Graph Queries (SQL/PGQ)

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, assam258(at)gmail(dot)com
Cc: Junwang Zhao <zhjwpku(at)gmail(dot)com>, zengman <zengman(at)halodbtech(dot)com>, 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-03-25 08:41:42
Message-ID: 6fc1c996-93b1-43df-ba13-e94933cf3dfb@eisentraut.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 20.03.26 14:42, Ashutosh Bapat wrote:
>> We should either:
>>
>> (1) Support G041 fully -- both directions. Junwang's patch handles
>> this cleanly with minimal code change, or
>> (2) Not support G041 -- reject all non-local element pattern
>> references, throwing an error for both directions.
>>
>> What do you think?
>
> We will support the cross variable references in future once we
> support more path patterns leading to a more mature code in that area.
> But it doesn't harm to support backward references which can be easily
> supported now. I don't see the code to do so getting disturbed as it
> matures. For the segmentation fault a simple fix to add graph_pattern
> suffices for now. Let's see if Peter has a different opinion.

I think we should not allow non-local references in either direction
(until we implement feature G041), option 2 above. Allowing only
backward references seems kind of an arbitrary implementation artifact.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Smith 2026-03-25 08:48:32 Re: Initial COPY of Logical Replication is too slow
Previous Message Amit Kapila 2026-03-25 08:25:05 Re: [Proposal] Adding Log File Capability to pg_createsubscriber