|From:||Antonin Houska <ah(at)cybertec(dot)at>|
|Subject:||Re: WIP: Aggregation push-down|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
Antonin Houska <ah(at)cybertec(dot)at> wrote:
> Antonin Houska <ah(at)cybertec(dot)at> wrote:
> > This is a new version of the patch I presented in .
> cat .git/refs/heads/master
This is another version of the patch.
Besides other changes, it enables the aggregation push-down for postgres_fdw,
although only for aggregates whose transient aggregation state is equal to the
output type. For other aggregates (like avg()) the remote nodes will have to
return the transient state value in an appropriate form (maybe bytea type),
which does not depend on PG version.
shard.tgz demonstrates the typical postgres_fdw use case. One query shows base
scans of base relation's partitions being pushed to shard nodes, the other
pushes down a join and performs aggregation of the join result on the remote
node. Of course, the query can only references one particular partition, until
the "partition-wise join"  patch gets committed and merged with this my
One thing I'm not sure about is whether the patch should remove
GetForeignUpperPaths function from FdwRoutine, which it essentially makes
obsolete. Or should it only be deprecated so far? I understand that
deprecation is important for "ordinary SQL users", but FdwRoutine is an
interface for extension developers, so the policy might be different.
Any feedback is appreciated.
|Next Message||Konstantin Knizhnik||2017-08-17 15:28:04||Re: [PATCH] Push limit to sort through a subquery|
|Previous Message||Tom Lane||2017-08-17 15:21:30||Re: [HACKERS] [postgresql 10 beta3] unrecognized node type: 90|