Re: BUG #18568: BUG: Result wrong when do group by on partition table!
От | Aleksander Alekseev |
---|---|
Тема | Re: BUG #18568: BUG: Result wrong when do group by on partition table! |
Дата | |
Msg-id | CAJ7c6TPD+KMeT19jaoXjPf8_4mdQWOYXzOEyCuFDGanv=_k8UQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: BUG #18568: BUG: Result wrong when do group by on partition table! (Tender Wang <tndrwang@gmail.com>) |
Ответы |
回复: BUG #18568: BUG: Result wrong when do group by on partition table!
|
Список | pgsql-bugs |
Hi, > [...] > I continue to find out why the collation id of partkey is 16384(e.g. case_insensitive). The partkey expr info is > set in set_baserel_partition_key_exprs(), which it uses partkey->parttypcoll[cnt] value not partkey->partcollation value. > > And partkey->parttypcoll[cnt] is assigned from pg_attribute , which is the column c meta data. > Should we use partkey->partcollation value? I try to fix that in the attached patch. I add your case in the test, andI don't find > failed regress. ``` +SELECT c collate case_insensitive, count(c) FROM +pagg_tab_col GROUP BY c collate case_insensitive; + c | count +---+------- + e | 600 + D | 600 + C | 600 + B | 600 + A | 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
В списке pgsql-bugs по дате отправления: