Re: BUG #18568: BUG: Result wrong when do group by on partition table!
| От | Tender Wang |
|---|---|
| Тема | Re: BUG #18568: BUG: Result wrong when do group by on partition table! |
| Дата | |
| Msg-id | CAHewXN=4JGyH+unrdAxSWOwU+dN1vPB434iCye+P8WS4_LPwHw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: BUG #18568: BUG: Result wrong when do group by on partition table! (Amit Langote <amitlangote09@gmail.com>) |
| Ответы |
Re: BUG #18568: BUG: Result wrong when do group by on partition table!
|
| Список | pgsql-bugs |
Amit Langote <amitlangote09@gmail.com> 于2024年10月22日周二 15:33写道：
Not really. As the documentation says, collation can be specified per
column or per operation:
https://www.postgresql.org/docs/current/collation.html
In this case, the operation is partitioning. When you specify the
COLLATE clause for a partition key, it means that the partitioning
logic, such as partition tuple routing, will use that collation
instead of the column-specified or the column type's collation.
Since you said partition key had its own collation, and but we used column type's collation in
set_baserel_partition_key_exprs() as below:
partexpr = (Expr *) makeVar(varno, attno,
partkey->parttypid[cnt],
partkey->parttypmod[cnt],
partkey->parttypcoll[cnt], 0);
partkey->parttypid[cnt],
partkey->parttypmod[cnt],
partkey->parttypcoll[cnt], 0);
I think why not we directly use the partition key collation(e.g. partcollation).
Thanks,
Tender Wang
В списке pgsql-bugs по дате отправления: