| 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:37:50 |
| Message-ID: | 344971.1618868270@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
James Coleman <jtc331(at)gmail(dot)com> writes:
> I forgot to comment on this in my previous email, but it seems to me
> that relation_has_safe_ec_member, while less wordy, isn't quite
> descriptive enough. Perhaps something like
> relation_has_sort_safe_ec_member?
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2021-04-19 21:38:43 | Re: Allowing to create LEAKPROOF functions to non-superuser |
| Previous Message | Andrew Dunstan | 2021-04-19 21:28:02 | Re: Reduce the number of special cases to build contrib modules on windows |