From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Ruben Buchatskiy <ruben(at)ispras(dot)ru> |
Cc: | Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Thom Brown <thom(at)linux(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com> |
Subject: | Re: GSoC 2017 |
Date: | 2017-02-08 16:06:17 |
Message-ID: | CA+Tgmoa=kzHJ+TwxyQ+vKu21nk3prkRjSdbhjubN7qvc8UKuGg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Feb 6, 2017 at 6:51 AM, Ruben Buchatskiy <ruben(at)ispras(dot)ru> wrote:
> 2017-01-10 12:53 GMT+03:00 Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>:
>> 1. What project ideas we have?
>
> We would like to propose a project on rewriting PostgreSQL executor from
>
> traditional Volcano-style [1] to so-called push-based architecture as
> implemented in
>
> Hyper [2][3] and VitesseDB [4]. The idea is to reverse the direction of data
> flow
>
> control: instead of pulling up tuples one-by-one with ExecProcNode(), we
> suggest
>
> pushing them from below to top until blocking operator (e.g. Aggregation) is
>
> encountered. There’s a good example and more detailed explanation for this
> approach in [2].
I think this very possibly a good idea but extremely unlikely to be
something that a college student or graduate student can complete in
one summer. More like an existing expert developer and a year of
doing not much else.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2017-02-08 16:07:51 | Re: drop support for Python 2.3 |
Previous Message | Tom Lane | 2017-02-08 16:00:09 | Re: chomp PQerrorMessage() in backend uses |