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 CAExHW5uNa3m0bJtw4oJVh8=5Or71H4TDH0f5Mgz3CFf5B2YMmg@mail.gmail.com
Whole thread Raw
In response to Re: SQL Property Graph Queries (SQL/PGQ)  (Henson Choi <assam258@gmail.com>)
Responses Re: SQL Property Graph Queries (SQL/PGQ)
List pgsql-hackers
On Thu, Jan 22, 2026 at 5:26 PM Henson Choi <assam258@gmail.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



pgsql-hackers by date:

Previous
From: jian he
Date:
Subject: Re: Change COPY ... ON_ERROR ignore to ON_ERROR ignore_row
Next
From: Peter Eisentraut
Date:
Subject: Re: SQL:2011 Application Time Update & Delete