Re: Wrong result when enable_partitionwise_join is on if collation of PartitionKey and Column is different.

From: Tender Wang <tndrwang(at)gmail(dot)com>
To: Amit Langote <amitlangote09(at)gmail(dot)com>
Cc: Junwang Zhao <zhjwpku(at)gmail(dot)com>, jian he <jian(dot)universality(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Wrong result when enable_partitionwise_join is on if collation of PartitionKey and Column is different.
Date: 2024-11-01 02:59:21
Message-ID: CAHewXNk=FAwF5P1BX+3sEWH4vr_JLmXG-pJV8Q0n=ZXHaDtTAQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Amit Langote <amitlangote09(at)gmail(dot)com> 于2024年10月31日周四 21:09写道：

>
> 0001 is the patch for the partitionwise grouping issue (bug #18568).
> I concluded that even partial aggregate should be disallowed when the
> grouping collation doesn't match partitioning collation. The result
> with partial partitionwise grouping is not the same as when
> enable_partitionwise_aggregate is off.
>

LGTM

--
Thanks,
Tender Wang

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message 李奇隆 2024-11-01 03:13:09 PG does not support one function of its extension pg_hint_plan
Previous Message Tender Wang 2024-11-01 02:39:35 Re: Wrong result when enable_partitionwise_join is on if collation of PartitionKey and Column is different.