回复: BUG #18568: BUG: Result wrong when do group by on partition table!

From: 狂奔的蜗牛 <1105066510(at)qq(dot)com>
To: Aleksander Alekseev <aleksander(at)timescale(dot)com>, pgsql-bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Cc: Tender Wang <tndrwang(at)gmail(dot)com>
Subject: 回复: BUG #18568: BUG: Result wrong when do group by on partition table!
Date: 2024-08-06 11:45:59
Message-ID: tencent_6767E6371361847E7540172904F06C1A1908@qq.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,
I am working to compatible with Oracle in PG,
in oracle, the result used case-insensitive collation is not&nbsp;unique.
There are two oracle's test case:

first case:
```sql
&nbsp; &nbsp; CREATE TABLE group_by_ci_test_1 (c varchar2(20));
&nbsp; &nbsp; INSERT INTO group_by_ci_test_1 VALUES ('a');
&nbsp; &nbsp; INSERT INTO group_by_ci_test_1 VALUES ('a');
&nbsp; &nbsp; INSERT INTO group_by_ci_test_1 VALUES ('A');
&nbsp; &nbsp; SELECT c collate binary_ci, count(c) FROM group_by_ci_test_1 GROUP BY c collate binary_ci;
```
first result
```shell
&nbsp; &nbsp; CCOLLATEBINARY_CI&nbsp; &nbsp; &nbsp; COUNT(C)
&nbsp; &nbsp; -------------------- ----------
&nbsp; &nbsp; a&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;3

```

second case:
```sql
&nbsp; &nbsp; CREATE TABLE group_by_ci_test_2 (c varchar2(20));
&nbsp; &nbsp; INSERT INTO group_by_ci_test_2 VALUES ('A');
&nbsp; &nbsp; INSERT INTO group_by_ci_test_2 VALUES ('a');
&nbsp; &nbsp; INSERT INTO group_by_ci_test_2 VALUES ('a');
&nbsp; &nbsp; SELECT c collate binary_ci, count(c) FROM group_by_ci_test_2 GROUP BY c collate binary_ci;

```
second result:
```shell
&nbsp; &nbsp; CCOLLATEBINARY_CI&nbsp; &nbsp; &nbsp; COUNT(C)
&nbsp; &nbsp; -------------------- ----------
&nbsp; &nbsp; A&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;6

```

狂奔的蜗牛
1105066510(at)qq(dot)com

&nbsp;

------------------&nbsp;原始邮件&nbsp;------------------
发件人: "Aleksander Alekseev" <aleksander(at)timescale(dot)com&gt;;
发送时间:&nbsp;2024年8月6日(星期二) 下午5:09
收件人:&nbsp;"pgsql-bugs"<pgsql-bugs(at)lists(dot)postgresql(dot)org&gt;;
抄送:&nbsp;"Tender Wang"<tndrwang(at)gmail(dot)com&gt;;"狂奔的蜗牛"<1105066510(at)qq(dot)com&gt;;
主题:&nbsp;Re: BUG #18568: BUG: Result wrong when do group by on partition table!

Hi,

&gt; [...]
&gt; I continue to find out why the collation id of partkey is 16384(e.g. case_insensitive). The partkey expr info is
&gt; set in set_baserel_partition_key_exprs(), which it uses partkey-&gt;parttypcoll[cnt] value not&nbsp; partkey-&gt;partcollation value.
&gt;
&gt; And partkey-&gt;parttypcoll[cnt] is assigned from pg_attribute , which is the column c meta data.
&gt; Should we use partkey-&gt;partcollation value?&nbsp; I try to fix that in the attached patch. I add your case in the test, and I don't find
&gt; failed regress.

```
+SELECT c collate case_insensitive, count(c) FROM
+pagg_tab_col GROUP BY c collate case_insensitive;
+ c | count
+---+-------
+ e |&nbsp;&nbsp; 600
+ D |&nbsp;&nbsp; 600
+ C |&nbsp;&nbsp; 600
+ B |&nbsp;&nbsp; 600
+ A |&nbsp;&nbsp; 600
+(5 rows)
```

Shouldn't we use UPPER(c) and ORDER BY in the test case to make the
results deterministic?

--
Best regards,
Aleksander Alekseev

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Sahu, Abhisek Kumar 2024-08-06 12:01:14 RE: BUG #18569: Memory leak in Postgres Enterprise server
Previous Message 狂奔的蜗牛 2024-08-06 11:33:16 回复: BUG #18568: BUG: Result wrong when do group by on partition table!