| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
| Cc: | Alastair McKinley <a(dot)mckinley(at)analyticsengines(dot)com>, "pgsql-general\(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Possible bug: SQL function parameter in window frame definition |
| Date: | 2019-09-30 20:25:36 |
| Message-ID: | 6831.1569875136@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> writes:
> "Tom" == Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> Tom> Hmm. I think this is a reasonable direction to go in, but
> Tom> what about groupingSets and rowMarks?
> groupingSets ultimately contains nothing but numbers which are
> meaningless without reference to the matching groupClause list. So
> anything that cares about those is really going to have to process them
> in its Query case in the walker function in order to get at both
> clauses.
Ah. I was thinking there were SortGroupClauses under them, but that
was based on an overly hasty reading of the parsenodes.h comments.
No further complaints.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2019-09-30 20:29:15 | Re: pg_upgrade (Checking for reg* data types) |
| Previous Message | Joe Horsnell | 2019-09-30 20:02:47 | Behaviour adding a column with and without a default (prior to PG11) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2019-09-30 20:34:13 | Re: Memory Accounting |
| Previous Message | Robert Haas | 2019-09-30 19:55:54 | Re: pgsql: Implement jsonpath .datetime() method |