Camelia,
While that provides a guideline for what you'll want to include in your
proposal, I believe you have some amount of freedom both in how much you
cover each of those topic areas and the ordering of them. You are also
welcome to include any other information which is relevant and supports
your proposal.
Thanks!
Stephen
* Camelia C (camelia13c@gmail.com) wrote:
> Hello,
>
> For my second question, I guess that [1] provides the information of the
> expected parts of the project proposal.
>
> However, I expect some feedback from your part about the topic chosen
> before I jump into writing the project proposal.
>
> Thanks!
>
> Have a nice week-end,
> Camelia
>
> [1] http://www.postgresql.org/developer/summerofcode/#proposals
>
>
> ---------- Forwarded message ----------
> From: Camelia C <camelia13c@gmail.com>
> Date: Thu, Mar 5, 2015 at 3:54 AM
> Subject: [GSoC] Optimization tasks
> To: pgsql-students@postgresql.org
>
>
> Hello,
>
> My name is Camelia, I carry out Doctoral/PhD research in the field of
> database query processing and I'd like to contribute with PostgreSQL
> optimization tasks during this year's GSoC:
>
> - Optimization- add to the join removal code the ability to remove joins
> to tables when the join is on a foreign key column (where all entries must
> exist in the parent anyway)
> - Optimization- Check the set of conditionals on a WHERE clause against
> CHECK constraints on the table being queried and remove any conditionals
> which *must* be true due to the CHECK constraints
>
> and others that may appear interesting along my review of the source code.
>
> I'm very excited about this opportunity and I hope that the results will be
> as good!
>
> Will the aforementioned subjects be open for work or do other committers
> have them under work already?
> Do you have a specific template for the project proposal?
>
> Thank you very much!
>
> Best regards,
> Camelia