| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "colinthart(at)gmail(dot)com" <colinthart(at)gmail(dot)com>, "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: SEQUENCE keyword is option on GRANT |
| Date: | 2025-03-31 13:55:51 |
| Message-ID: | CAKFQuwb0A=26P0YyRBx2G6ywDKzyxrBKuCHE3_F1D-U3ePdN5w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Monday, March 31, 2025, PG Doc comments form <noreply(at)postgresql(dot)org>
wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/17/sql-grant.html
> Description:
>
> The documentation indicates that they keyword SEQUENCE must precede the
> sequence_name in a GRANT, but in my experience it is optional:
>
> colin(at)adinkra:~$ psql
> psql (17.4 (Debian 17.4-1.pgdg120+2))
> Type "help" for help.
>
> colin(at)[local]:colin=> create sequence x;
> CREATE SEQUENCE
> colin(at)[local]:colin=> grant select on x to public; -- should fail but
> works
>
>
Sequences are relations (see pg_class) so the [TABLE] variant is able to
target them, which is what you’ve written here.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | jian he | 2025-04-01 00:20:47 | Re: SEQUENCE keyword is option on GRANT |
| Previous Message | PG Doc comments form | 2025-03-31 10:29:28 | SEQUENCE keyword is option on GRANT |