Re: SQL Property Graph Queries (SQL/PGQ)

From: Henson Choi <assam258(at)gmail(dot)com>
To: Junwang Zhao <zhjwpku(at)gmail(dot)com>
Cc: 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-03-08 11:30:39
Message-ID: CAAAe_zDgc-G20EdJwoFk2mV25LeuqHh66AeX39s6GSkx37fNjQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Junwang,

> 1.3 Supported by Oracle, not PG
> >
> > a.* star reference in COLUMNS
> > Oracle allows COLUMNS (a.*) to return all properties of an element
> > variable across all its labels. PG rejects this ("*" not allowed
> > here). A workaround exists: list properties explicitly. This is the
> > only SQL/PGQ query execution capability where Oracle is ahead of the
> > current PG implementation.
>
> PGQ doesn’t seem to reject a.*. I think PostgreSQL is still at an early
> stage
> of supporting SQL/PGQ, so missing features like this are acceptable for
> now, and we can add support for more syntax in the future.
>

I agree — a.* in COLUMNS is better addressed in a follow-up patch.

Regards,
Henson

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Henson Choi 2026-03-08 14:24:55 Re: Row pattern recognition
Previous Message Junwang Zhao 2026-03-08 11:09:51 Re: SQL Property Graph Queries (SQL/PGQ)