| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| 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>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Subject: | Re: "could not find pathkey item to sort" for TPC-DS queries 94-96 |
| Date: | 2021-04-19 21:42:04 |
| Message-ID: | 345181.1618868524@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I wrote:
> I'm not wedded to that name, certainly, but it seems like neither
> of these is quite getting at the issue. An EC can be sorted on,
> by definition, but there are some things we don't want to sort
> on till the final output step. I was trying to think of something
> using the terminology "early sort", but didn't much like
> "relation_has_early_sortable_ec_member" or obvious variants of that.
... or, as long as it's returning a boolean, maybe it could be
"relation_can_be_sorted_early" ?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-04-19 22:09:51 | Re: "could not find pathkey item to sort" for TPC-DS queries 94-96 |
| Previous Message | Tom Lane | 2021-04-19 21:40:31 | Re: Implementing Incremental View Maintenance |