From: | Alexander Lakhin <exclusion(at)gmail(dot)com> |
---|---|
To: | David Rowley <dgrowleyml(at)gmail(dot)com>, Richard Guo <guofenglinux(at)gmail(dot)com> |
Cc: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: pg16: XX000: could not find pathkey item to sort |
Date: | 2024-03-13 17:00:00 |
Message-ID: | cf63174c-8c89-3953-cb49-48f41f74941a@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello David,
09.10.2023 07:13, David Rowley wrote:
> On Mon, 9 Oct 2023 at 12:42, David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
>> Maybe it's worth checking the total planning time spent in a run of
>> the regression tests with and without the patch to see how much
>> overhead it adds to the "average case".
> I've now pushed the patch that trims off the Pathkeys for the ORDER BY
> / DISTINCT aggregates.
>
I've stumbled upon the same error, but this time it apparently has another
cause. It can be produced (on REL_16_STABLE and master) as follows:
CREATE TABLE t (a int, b int) PARTITION BY RANGE (a);
CREATE TABLE td PARTITION OF t DEFAULT;
CREATE TABLE tp1 PARTITION OF t FOR VALUES FROM (1) TO (2);
SET enable_partitionwise_aggregate = on;
SET parallel_setup_cost = 0;
SELECT a, sum(b order by b) FROM t GROUP BY a ORDER BY a;
ERROR: could not find pathkey item to sort
`git bisect` for this anomaly blames the same commit 1349d2790.
Best regards,
Alexander
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2024-03-13 17:12:01 | Re: Reports on obsolete Postgres versions |
Previous Message | Jeff Davis | 2024-03-13 16:49:26 | Re: un-revert the MAINTAIN privilege and the pg_maintain predefined role |