From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Rushabh Lathia <rushabh(dot)lathia(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: wrong query result with jit_above_cost= 0 |
Date: | 2018-06-26 18:23:06 |
Message-ID: | 20180626182306.nnzibgdnvladfsep@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On 2018-06-26 23:50:32 +0530, Rushabh Lathia wrote:
> I found the below query which returns the wrong output
> when jit_above_cost= 0 is set.
>
> Steps to reproduce:
>
> CREATE TABLE emp (
> epno NUMERIC(4),
> ename VARCHAR(10),
> job VARCHAR(9),
> mgr NUMERIC(4),
> hiredate DATE,
> sal NUMERIC(7,2),
> comm NUMERIC(7,2),
> deptno NUMERIC(2)
> );
>
> INSERT INTO emp VALUES (7369,'SMITH','CLERK',7902,'17-DEC-80',800,NULL,20);
> INSERT INTO emp VALUES
> (7499,'ALLEN','SALESMAN',7698,'20-FEB-81',1600,300,30);
>
> set jit_above_cost= 0;
>
> select max(epno) from emp group by rollup((deptno,epno)) order by 1 asc;
>
> without the ROLLUP, I don't see any problem with results.
Interesting. I've opened an open item referencing this.
Greetings,
Andres Freund
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2018-06-26 18:42:38 | Re: Fix slot's xmin advancement and subxact's lost snapshots in decoding. |
Previous Message | AJG | 2018-06-26 18:20:56 | Re: Global shared meta cache |