Re: BUG #15262: "unexpected end of tuplestore" error when using new GROUPS window function clause

Lukas Eder <lukas.eder@gmail.com>

From: Lukas Eder <lukas.eder@gmail.com>

To: Tom Lane <tgl@sss.pgh.pa.us>

Cc: pgsql-bugs@lists.postgresql.org

Date: 2018-07-10T07:29:51Z

Lists: pgsql-bugs

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Fix bugs with degenerate window ORDER BY clauses in GROUPS/RANGE mode.
- 8893d48e7fbf 11.0 landed
- ff4f8891648c 12.0 landed

Am Di., 10. Juli 2018 um 00:29 Uhr schrieb Tom Lane <tgl@sss.pgh.pa.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.