From: | Thom Brown <thom(at)linux(dot)com> |
---|---|
To: | magnus(dot)johan(dot)hedberg(at)gmail(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: Reserved word: OWNER |
Date: | 2022-05-13 12:53:05 |
Message-ID: | CAA-aLv4EJmU2OCPugoknebZDUMXr=cX+tDkKt6Lp47h-kw_1TA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Fri, 13 May 2022 at 13:23, 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/14/sql-keywords-appendix.html
> Description:
>
> You say it's a non-reserved word, but on this page:
> https://www.postgresql.org/docs/current/sql-alterdatabase.html#:~:text=To%20alter%20the%20owner%2C%20you,default%20tablespace%20of%20the%20database.
>
> you clearly use OWNER as a reserved word:
>
> ALTER DATABASE name OWNER TO { new_owner | CURRENT_ROLE | CURRENT_USER |
> SESSION_USER }
>
> and if I try to use OWNER as a column name in pgAdmin, it is marked blue (ie
> a reserved word). So which is it?
That sounds like a PgAdmin issue, and probably because of the way that
their syntactic highlighting works. OWNER isn't a reserved word.
postgres=# CREATE TABLE owner (owner TEXT);
CREATE TABLE
postgres=# \d owner
Table "public.owner"
Column | Type | Collation | Nullable | Default
--------+------+-----------+----------+---------
owner | text | | |
Regards
Thom
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2022-05-13 13:33:21 | Re: Reserved word: OWNER |
Previous Message | PG Doc comments form | 2022-05-13 07:40:57 | Reserved word: OWNER |