Re: gram.y comment issue

From: Amit Langote <amitlangote09(at)gmail(dot)com>
To: 张文升 <wensheng(dot)zhang(at)qunar(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: gram.y comment issue
Date: 2016-03-09 12:54:29
Message-ID: CA+HiwqE=_VkCvzUATY5GUTwiBFbXRpQzKLg4yjGm7Hn1=c4Wyg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Mar 9, 2016 at 3:04 PM, 张文升 <wensheng(dot)zhang(at)qunar(dot)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.

> 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.

Thanks,
Amit

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Stepya 2016-03-09 13:39:03 BUG #14008: corr, covar_pop function returns different values on the same dataset
Previous Message Valeriy A. 2016-03-09 10:46:36 Re: BUG #13920: pg_try_advisory_xact_lock bigint trouble