Re: SQL Property Graph Queries (SQL/PGQ)

From: Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>
To: assam258(at)gmail(dot)com
Cc: Ajay Pal <ajay(dot)pal(dot)k(at)gmail(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Amit Langote <amitlangote09(at)gmail(dot)com>, Junwang Zhao <zhjwpku(at)gmail(dot)com>, Vik Fearing <vik(at)postgresfriends(dot)org>, 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-22 14:50:46
Message-ID: CAExHW5uNa3m0bJtw4oJVh8=5Or71H4TDH0f5Mgz3CFf5B2YMmg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jan 22, 2026 at 5:26 PM Henson Choi <assam258(at)gmail(dot)com> wrote:
>
> Hi Ajay,
>
> I looked into this and it appears to be expected PostgreSQL behavior rather than a GRAPH_TABLE-specific issue.

+1. This behaviour is documented in [1]

"
Inherited queries perform access permission checks on the parent table
only. Thus, for example, granting UPDATE permission on the cities
table implies permission to update rows in the capitals table as well,
when they are accessed through cities. This preserves the appearance
that the data is (also) in the parent table. But the capitals table
could not be updated directly without an additional grant. In a
similar way, the parent table's row security policies (see Section
5.9) are applied to rows coming from child tables during an inherited
query. A child table's policies, if any, are applied only when it is
the table explicitly named in the query; and in that case, any
policies attached to its parent(s) are ignored.
"

[1] https://www.postgresql.org/docs/current/ddl-inherit.html#:~:text=In%20a%20similar%20way%2C%20the%20parent%20table's,policies%20attached%20to%20its%20parent(s)%20are%20ignored.

--
Best Wishes,
Ashutosh Bapat

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2026-01-22 15:21:54 Re: SQL:2011 Application Time Update & Delete
Previous Message jian he 2026-01-22 14:45:10 Re: Change COPY ... ON_ERROR ignore to ON_ERROR ignore_row