From: | Dmitry Dolgov <9erthalion6(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: LLVM jit and window functions on a temporary table |
Date: | 2018-07-22 10:34:59 |
Message-ID: | CA+q6zcUpGip3pwSZRnYNan1vTiPuuror7OR8pn2snmb5TTdqfQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
> On Sat, 21 Jul 2018 at 22:33, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Dmitry Dolgov <9erthalion6(at)gmail(dot)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(at)sss(dot)pgh(dot)pa(dot)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!
From | Date | Subject | |
---|---|---|---|
Next Message | PG Bug reporting form | 2018-07-22 18:30:29 | BUG #15290: Stuck Parallel Index Scan query |
Previous Message | Nick Farmer | 2018-07-22 00:29:52 | Re: BUG #15289: Type inference of parameters in prepared statements can sometimes fail or succeed, depending... |