From: | Tender Wang <tndrwang(at)gmail(dot)com> |
---|---|
To: | 1105066510(at)qq(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #18568: BUG: Result wrong when do group by on partition table! |
Date: | 2024-08-06 13:23:44 |
Message-ID: | CAHewXNkch_=oOjc5P=E9WmxQXBvA8ju0+7Fed6=e9FGWgmBCLA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
PG Bug reporting form <noreply(at)postgresql(dot)org> 于2024年8月6日周二 15:01写道:
> The following bug has been logged on the website:
>
> Bug reference: 18568
> Logged by: Webbo Han
> Email address: 1105066510(at)qq(dot)com
> PostgreSQL version: 16.3
> Operating system: centos 7.6
> Description:
>
> First, we create one case-insensitive collation use ICU:
> ```sql
> CREATE COLLATION case_insensitive (
> provider = icu,
> locale = 'und-u-ks-level2',
> deterministic = false
> );
> ```
>
> Then, we create the partition table, meanwhile we set the collation of
> column c to `case_insensitive`,
> and set partkey's collation to 'C'.
> ```sql
> SET enable_partitionwise_aggregate TO true;
> SET enable_partitionwise_join TO true;
> SET max_parallel_workers_per_gather TO 0;
> SET enable_incremental_sort TO off;
> CREATE TABLE pagg_tab (c text collate case_insensitive) PARTITION
> BY LIST(c
> collate "C");
>
I think above create table again. Should we allow this CREATE TABLE? The
partition key
definition are not same with column definiton. Is it better to report
error for users?
--
Tender Wang
From | Date | Subject | |
---|---|---|---|
Next Message | Tender Wang | 2024-08-06 14:37:56 | Re: BUG #18568: BUG: Result wrong when do group by on partition table! |
Previous Message | Sahu, Abhisek Kumar | 2024-08-06 12:01:14 | RE: BUG #18569: Memory leak in Postgres Enterprise server |