| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | James Coleman <jtc331(at)gmail(dot)com> |
| Cc: | Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, Luc Vlaming <luc(at)swarm64(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: "could not find pathkey item to sort" for TPC-DS queries 94-96 |
| Date: | 2021-04-15 00:21:59 |
| Message-ID: | CA+TgmoZ5OY_J_eHSv9cf9u0FHEPU2Pck+5RLtLfORn0Z8B=e_Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Apr 14, 2021 at 8:20 PM James Coleman <jtc331(at)gmail(dot)com> wrote:
> > Hmm, could be. Although, the stack trace at issue doesn't seem to show
> > a call to create_incrementalsort_plan().
>
> The changes to gather merge path generation made it possible to use
> those paths in more cases for both incremental sort and regular sort,
> so by "incremental sort" I read Tomas as saying "the patches that
> brought in incremental sort" not specifically "incremental sort
> itself".
I agree. That's why I said "hmm, could be" even though the plan
doesn't involve one.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | James Coleman | 2021-04-15 00:39:17 | Re: "could not find pathkey item to sort" for TPC-DS queries 94-96 |
| Previous Message | Andres Freund | 2021-04-15 00:21:58 | Re: New IndexAM API controlling index vacuum strategies |