From: Antonin Houska <ah@cybertec.at>
To: pgsql-hackers@postgresql.org
Subject: Re: WIP: Aggregation push-down
Date: Fri, 03 Nov 2017 16:33:45 +0100
Message-ID: <14577.1509723225@localhost> (raw)
In-Reply-To: <29613.1502983342@localhost>
References: <9666.1491295317@localhost>
<8160.1493369169@localhost>
<29613.1502983342@localhost>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
Antonin Houska <ah@cybertec.at> wrote:
> This is another version of the patch.
> 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" [1] patch gets committed and merged with this my
> patch.
Since [1] is already there, the new version of shard.tgz shows what I consider
the typical use case. (I'm aware of the postgres_fdw regression test failures,
I'll try to fix them all in the next version.)
Besides that:
* A concept of "path unique keys" has been introduced. It helps to find out if
the final relation appears to generate a distinct set of grouping keys. If
that happens, the final aggregation is replaced by mere call of aggfinalfn()
function on each transient state value.
* FDW can sort rows by aggregate.
* enable_agg_pushdown GUC was added. The default value is false.
* I fixed errors reported during the previous CF.
* Added a few more regression tests.
I'm not about to add any other features now. Implementation of the missing
parts (see the TODO comments in the code) is the next step. But what I'd
appreciate most is a feedback on the design. Thanks.
> [1] https://commitfest.postgresql.org/14/994/
--
Antonin Houska
Cybertec Schönig & Schönig GmbH
Gröhrmühlgasse 26
A-2700 Wiener Neustadt
Web: http://www.postgresql-support.de, http://www.cybertec.at
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackersAttachments:
[application/x-gzip] agg_pushdown_v4.tgz (102.3K, ../14577.1509723225@localhost/2-agg_pushdown_v4.tgz)
download
[application/x-gzip] shard.tgz (1.4K, ../14577.1509723225@localhost/3-shard.tgz)
download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: ah@cybertec.at
Subject: Re: WIP: Aggregation push-down
In-Reply-To: <14577.1509723225@localhost>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox