From: | Antonin Houska <ah(at)cybertec(dot)at> |
---|---|
To: | Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Problems with plan estimates in postgres_fdw |
Date: | 2019-02-22 15:21:41 |
Message-ID: | 30939.1550848901@localhost |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp> wrote:
> (2019/02/08 21:35), Etsuro Fujita wrote:
> > (2019/02/08 2:04), Antonin Houska wrote:
> >> * regression tests: I think test(s) should be added for queries that have
> >> ORDER BY clause but do not have GROUP BY (and also no LIMIT / OFFSET)
> >> clause. I haven't noticed such tests.
> >
> > Will do.
>
> I noticed that such queries would be processed by what we already have for
> sort pushdown (ie, add_paths_with_pathkeys_for_rel()). I might be missing
> something, though.
What about an ORDER BY expression that contains multiple Var nodes? For
example
SELECT * FROM foo ORDER BY x + y;
I think the base relation should not be able to generate paths with the
corresponding pathkeys, since its target should (besides PlaceHolderVars,
which should not appear in the plan of this simple query at all) only emit
individual Vars.
--
Antonin Houska
https://www.cybertec-postgresql.com
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2019-02-22 15:26:44 | Re: boolean and bool in documentation |
Previous Message | Euler Taveira | 2019-02-22 15:10:20 | Re: psql show URL with help |