From: Tom Lane <tgl@sss.pgh.pa.us>
To: 谭忠涛 <zhongtao.tan@seaboxdata.com>
Cc: pgsql-bugs <pgsql-bugs@lists.postgresql.org>
Subject: Re: Incorrect sort result caused by ROLLUP and WHERE operation
Date: Thu, 02 Jan 2025 11:04:23 -0500
Message-ID: <270213.1735833863@sss.pgh.pa.us> (raw)
In-Reply-To: <tencent_4568C7826D8BDEF01BC56D3D@qq.com>
References: <tencent_4568C7826D8BDEF01BC56D3D@qq.com>
"=?utf-8?B?6LCt5b+g5rab?=" <zhongtao.tan@seaboxdata.com> writes:
> create table t1(a int, b int);
> insert into t1 values(1,1),(1,2);
> select a,b,sum(10) as s from t1 where a = 1 group by rollup(a,b) order by a, s desc;
Yeah. This is fixed in HEAD (v18-to-be) but the fix is too invasive
to consider back-patching. 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, zhongtao.tan@seaboxdata.com, pgsql-bugs@lists.postgresql.org
Subject: Re: Incorrect sort result caused by ROLLUP and WHERE operation
In-Reply-To: <270213.1735833863@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox