From: | Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp> |
---|---|
To: | Jinhua Luo <luajit(dot)io(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Is it possible for postgres_fdw to push down queries on co-located tables? |
Date: | 2018-09-20 09:16:30 |
Message-ID: | 5BA3656E.9030107@lab.ntt.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
(2018/09/18 23:20), Jinhua Luo wrote:
> Sorry, the example is not so proper. I just think even if it's a
> simple example, e.g. join two co-located tables, the planner should
> work out to push down it. Can you confirm the postgresql could detect
> co-located tables on the same foreign server and push down queries on
> them? Could you give an actual example or point out the relevant
> source code paths for reference?
>
> (Let me clarify the context of this question, if the planner supports
> co-located push-down, then it's meaningful for manual sharding via
> partitioning to remote tables, where it's mostly necessary to join two
> or more co-located parent tables in complex queries. If not, the
> postgresql instance on which the parent tables are placed (let's say
> it's a coordinator node) would be likely the bottleneck.)
You might want to check partitionwise join functionality as well, which
we have in PG11 [1].
Best regards,
Etsuro Fujita
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Munro | 2018-09-20 09:47:07 | Re: Size and size_t in dsa API |
Previous Message | Pavel Stehule | 2018-09-20 09:08:57 | Re: [HACKERS] proposal: schema variables |