Re: [bug] keyword commit being accepted for column name

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Vinícius Abrahão <vinnix(dot)bsd(at)gmail(dot)com>
Cc: "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: [bug] keyword commit being accepted for column name
Date: 2025-05-31 18:32:10
Message-ID: CAKFQuwYhaCTVc1AASYq1N4HhrYCtwraLyyxoA4YU6-E3EqNfuw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Saturday, May 31, 2025, Vinícius Abrahão <vinnix(dot)bsd(at)gmail(dot)com> wrote:

> postgres=# create table postgres_git_repository(commit text,
> first_line_commit text);
> CREATE TABLE
> postgres=# create table postgres_git_repository2("commit" text,
> first_line_commit text);
> CREATE TABLE
> postgres=# create table postgres_git_repository3("COMMIT" text,
> first_line_commit text);
> CREATE TABLE
>
>
Only the first of those is even valid here, if you double-quote an
identifier it never is even possibly considered a keyword that could
conflict. As for the first one, our reserved words specification doesn’t
claim commit as one of them. Bugs need to things where we claim one thing
and implement something different. Not relative to some external
specification.

David J.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2025-05-31 23:46:25 Re: BUG #18925: Heap-buffer-overflow: pglz_compress with pglz_stategy_always
Previous Message Kirk Parker 2025-05-31 18:22:08 Re: [bug] keyword commit being accepted for column name