Re: [bug] keyword commit being accepted for column name - Mailing list pgsql-bugs

From David G. Johnston
Subject Re: [bug] keyword commit being accepted for column name
Date
Msg-id CAKFQuwYhaCTVc1AASYq1N4HhrYCtwraLyyxoA4YU6-E3EqNfuw@mail.gmail.com
Whole thread Raw
In response to [bug] keyword commit being accepted for column name  (Vinícius Abrahão <vinnix.bsd@gmail.com>)
List pgsql-bugs
On Saturday, May 31, 2025, Vinícius Abrahão <vinnix.bsd@gmail.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.

pgsql-bugs by date:

Previous
From: Vinícius Abrahão
Date:
Subject: [bug] keyword commit being accepted for column name
Next
From: Tom Lane
Date:
Subject: Re: BUG #18925: Heap-buffer-overflow: pglz_compress with pglz_stategy_always