| From: | Shinya Kato <shinya11(dot)kato(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | doc: Add PROPERTY GRAPH to the access privilege tables |
| Date: | 2026-07-14 13:57:26 |
| Message-ID: | CAOzEurScgwLDXQmNFnDZANGAMMiva9GnLH_kO8qGtGVHUvVk2A@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi hackers,
Since SQL/PGQ was committed, the SELECT privilege can be granted on a
property graph, but property graphs are missing from the two summary
tables in the "Privileges" section of ddl.sgml.
The description of the SELECT privilege in that section already
mentions property graphs, and GRANT lists PROPERTY GRAPH as a
grantable object, yet the reference tables that follow do not:
- The privilege abbreviations table does not list PROPERTY GRAPH among
the object types the SELECT privilege applies to.
- The "Summary of Access Privileges" table has no PROPERTY GRAPH row.
The attached patch adds the missing entries.
--
Best regards,
Shinya Kato
NTT OSS Center
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-doc-Add-PROPERTY-GRAPH-to-the-access-privilege-ta.patch | application/octet-stream | 1.8 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2026-07-14 14:01:34 | Re: Fix GROUP BY ALL handling of ORDER BY operator semantics |
| Previous Message | Robert Haas | 2026-07-14 13:54:22 | document the dangers of granting TRIGGER or REFERENCES |