Thread

回复：Re: Incorrect sort result caused by ROLLUP and WHERE operation

谭忠涛 <zhongtao.tan@seaboxdata.com> — 2025-01-03T01:17:58Z

Thank you for your feedback.


regards


                    Tom Lane<tgl@sss.pgh.pa.us&gt;&nbsp;在 2025年1月3日 周五 0:04 写道：

"=?utf-8?B?6LCt5b+g5rab?=" <zhongtao.tan@seaboxdata.com&gt; writes:
&gt; create table t1(a int, b int);
&gt; insert into t1 values(1,1),(1,2);
&gt; select a,b,sum(10) as s from t1 where a = 1 group by rollup(a,b) order by a, s desc;

Yeah.&nbsp; This is fixed in HEAD (v18-to-be) but the fix is too invasive
to consider back-patching.&nbsp; Basically the problem is that older
versions don't understand that the post-ROLLUP value of "a" can be
different from the pre-ROLLUP value, so they think the "where a = 1"
clause removes any need to sort by "a".

As a workaround you could write something like "order by a+0, s desc"
to fool the optimizer into considering the ordering column to be
different from the value that's constrained by WHERE.

			regards, tom lane