Re: wrong query result with jit_above_cost= 0

Поиск
Список
Период
Сортировка
От Andres Freund
Тема Re: wrong query result with jit_above_cost= 0
Дата
Msg-id 20180626182306.nnzibgdnvladfsep@alap3.anarazel.de
обсуждение исходный текст
Ответ на wrong query result with jit_above_cost= 0  (Rushabh Lathia <rushabh.lathia@gmail.com>)
Ответы Re: wrong query result with jit_above_cost= 0  (Dmitry Dolgov <9erthalion6@gmail.com>)
Список 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


В списке pgsql-hackers по дате отправления:

Предыдущее
От: AJG
Дата:
Сообщение: Re: Global shared meta cache
Следующее
От: Alvaro Herrera
Дата:
Сообщение: Re: Fix slot's xmin advancement and subxact's lost snapshots indecoding.