Re: wrong results due to qual pushdown

2023-03-06 Thread Tom Lane
tender wang writes: > It looks wrong that the qual (e.g ((l_suppkey IS NOT NULL) OR > (getdatabaseencoding() !~~ CASE WHEN ($0 OR NULL::boolean) THEN NULL::text > ELSE NULL::text END))) is pushdown. I think this is the same issue reported at [1]. regards, tom lane [1] h

Re: wrong results due to qual pushdown

2023-03-06 Thread tender wang
Results on 16devel: c0 | c3 | c6 | c7 |c8 ++++--- 0 |||| ALGERIA 0 |||| ETHIOPIA 0 |||| KENYA 0 |||| MOROCCO 0 |||| MOZAMBIQUE 1 |||| ARGENTINA 1 |||

Re: wrong results due to qual pushdown

2023-03-06 Thread Ashutosh Bapat
On Mon, Mar 6, 2023 at 3:00 PM tender wang wrote: > tender wang > [image: 附件]14:51 (2小时前) > 发送至 pgsql-hackers > Hi hackers. >This query has different result on 16devel and 15.2. > select > sample_3.n_regionkey as c0, > ref_7.l_linenumber as c3, > sample_4.l_quantity as c6, >

wrong results due to qual pushdown

2023-03-06 Thread tender wang
tender wang [image: 附件]14:51 (2小时前) 发送至 pgsql-hackers Hi hackers. This query has different result on 16devel and 15.2. select sample_3.n_regionkey as c0, ref_7.l_linenumber as c3, sample_4.l_quantity as c6, sample_5.n_nationkey as c7, sample_3.n_name as c8 from public.