MIME-Version: 1.0
References: <165242765714.661.4834758786310673627@wrigleys.postgresql.org>
In-Reply-To: <165242765714.661.4834758786310673627@wrigleys.postgresql.org>
From: Thom Brown <thom@linux.com>
Date: Fri, 13 May 2022 13:53:05 +0100
Message-ID: 
 <CAA-aLv4EJmU2OCPugoknebZDUMXr=cX+tDkKt6Lp47h-kw_1TA@mail.gmail.com>
Subject: Re: Reserved word: OWNER
To: magnus.johan.hedberg@gmail.com, pgsql-docs@lists.postgresql.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: 
 <https://www.postgresql.org/message-id/CAA-aLv4EJmU2OCPugoknebZDUMXr%3DcX%2BtDkKt6Lp47h-kw_1TA%40mail.gmail.com>
Precedence: bulk

On Fri, 13 May 2022 at 13:23, PG Doc comments form
<noreply@postgresql.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