Re: gram.y comment issue - Mailing list pgsql-bugs

From Tom Lane
Subject Re: gram.y comment issue
Date
Msg-id 9732.1457537466@sss.pgh.pa.us
Whole thread Raw
In response to Re: gram.y comment issue  (Amit Langote <amitlangote09@gmail.com>)
Responses Re: gram.y comment issue  (张文升 <wensheng.zhang@qunar.com>)
List pgsql-bugs
Amit Langote <amitlangote09@gmail.com> writes:
> On Wed, Mar 9, 2016 at 3:04 PM, 张文升 <wensheng.zhang@qunar.com> wrote:
>> The gram.y  includes the line(line:1965):
>> /* ALTER TABLE <name> ALTER [COLUMN] <colname> SET ( column_parameter =
>> value [, ... ] ) */
>> ALTER opt_column ColId RESET reloptions
>> The comment has the word "SET", but I think that's should be "RESET".

> This one needs to be fixed.

Agreed, done.

>> src/include/nodes/parsenodes.h line:141
>> List      *distinctClause; /* a list of SortGroupClause's */
>> The comment has the word "SortGroupClause", but that's should be
>> "distinctClause".

> This one is fine.  The name distinctClause here is parser's way of
> referring to the SQL construct DISTINCT ON (<list-of-items>) in a
> SELECT query, where each member of the list is a SortGroupClause item.

Yes.  It might be surprising if you don't know that ORDER BY, GROUP BY,
and DISTINCT all have a common parsetree representation ... but the
comment is correct as written.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Amit Langote
Date:
Subject: Re: gram.y comment issue
Next
From: Nick Cleaton
Date:
Subject: streaming replication master can fail to shut down