> On Sat, 21 Jul 2018 at 22:33, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Dmitry Dolgov <9erthalion6@gmail.com> writes:
> > While testing PostgreSQL instance with enabled jit I found out another
> > interesting problem:
> > ...
> > gdb shows that in tuplestore_select_read_pointer somehow the value of ptr is -1
>
> Is that current HEAD, or back a bit? We just fixed a non-JIT-related
> bug with similar symptoms:
>
> Author: Tom Lane <tgl@sss.pgh.pa.us>
> Branch: master [ff4f88916] 2018-07-11 12:07:20 -0400
> Branch: REL_11_STABLE [8893d48e7] 2018-07-11 12:07:21 -0400
>
> Fix bugs with degenerate window ORDER BY clauses in GROUPS/RANGE mode.
>
> and your query does look like it matches that, since the f1=f2 clause
> renders the ORDER BY degenerate.
Yes, you're right - when I discovered the issue it was few commits before this
fix, and on the current HEAD it's not reproducible anymore. Thanks!