| From: | Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | Antonin Houska <ah(at)cybertec(dot)at> |
| 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-03-05 09:28:07 |
| Message-ID: | 5C7E4127.2030802@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
(2019/03/01 20:16), Antonin Houska wrote:
> Etsuro Fujita<fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp> wrote:
>> Conversely, it appears that add_foreign_ordered_paths() added by the patchset
>> would generate such pre-sorted paths *redundantly* when the input_rel is the
>> final scan/join relation. Will look into that.
>
> Currently I have no idea how to check the plan created by FDW at the
> UPPERREL_ORDERED stage, except for removing the sort from the
> UPPERREL_GROUP_AGG stage as I proposed here:
>
> https://www.postgresql.org/message-id/11807.1549564431%40localhost
I don't understand your words "how to check the plan created by FDW".
Could you elaborate on that a bit more?
Best regards,
Etsuro Fujita
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2019-03-05 09:34:43 | Re: [Proposal] Table-level Transparent Data Encryption (TDE) and Key Management Service (KMS) |
| Previous Message | David Rowley | 2019-03-05 09:22:26 | Re: NOT IN subquery optimization |