| From: | Lukas Eder <lukas(dot)eder(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #15262: "unexpected end of tuplestore" error when using new GROUPS window function clause |
| Date: | 2018-07-10 07:29:51 |
| Message-ID: | CAB4ELO6eoBx=PcwuFkHFq-_diRK-opcmZc5V9avhFZmxyWzB8A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Am Di., 10. Juli 2018 um 00:29 Uhr schrieb Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> I think what we really should be doing here is giving a parse error.
Yes, I agree. That's also what the SQL standard says.
ISO/IEC 9075-2:2016(E)
7.15 <window clause>
13 c) If GROUPS is specified, then:
i) Either WDEF shall contain a <window order clause>, or WDEF shall specify
an <existing window name> that identifies a window structure descriptor
that includes a window ordering clause.
> What would you expect GROUPS mode to do without an ORDER BY to define the
> grouping?
I had no expectations, was just playing around with the new syntax.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2018-07-10 08:59:03 | BUG #15271: Documentation / Error reporting on GUC parameter change |
| Previous Message | Noah Misch | 2018-07-10 01:43:08 | Extension relocation vs. schema qualification |