From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Amit Langote <amitlangote09(at)gmail(dot)com> |
Cc: | 张文升 <wensheng(dot)zhang(at)qunar(dot)com>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: gram.y comment issue |
Date: | 2016-03-09 15:31:06 |
Message-ID: | 9732.1457537466@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Amit Langote <amitlangote09(at)gmail(dot)com> writes:
> 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.
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
From | Date | Subject | |
---|---|---|---|
Next Message | Nick Cleaton | 2016-03-09 16:17:46 | streaming replication master can fail to shut down |
Previous Message | alexander | 2016-03-09 15:15:10 | BUG #14009: pg_restore not restoring privilegs when one login/group role is missing |