Re: GSOC - TOAST'ing in slices

From: Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>
To: George Papadrosou <gpapadrosou(at)gmail(dot)com>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: GSOC - TOAST'ing in slices
Date: 2017-03-15 12:20:32
Message-ID: CAPpHfds0R5PQYwkXM4qT1GyAcOCzk6WQB+2BR2k5ubM1edZuDw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Mar 15, 2017 at 5:03 AM, George Papadrosou <gpapadrosou(at)gmail(dot)com>
wrote:

> *Deliverables *
>
> - Implement “semantic” slicing for datatypes that support slicing into
> TOAST tables. These datatypes will be the Text, Array, JSON/JSONb and XML
> data types.
>

That looks too much comprehensive GSoC project for me. I would recommend
you to focus on more local task. For instance, providing better slicing
for jsonb with support of all relevant functions/operators looks pretty
enough work amount for GSoC project.
Remember, that the major target of GSoC project is to get it complete.
I.e. to produce patch in committable shape, not just a prototype. That's
quite ambitious, because this project also assumes some research. Thus,
there could be various approaches for slicing jsonb with different
advantages and disadvantages. So, I advice you to thought out approaches
you're going to try, and specify them in proposal. Schedule should include
prototyping each of these approaches, then testing and benchmarking to
selecting between them, then work on bringing selected approach to
committable shape.

------
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2017-03-15 12:35:49 Re: Microvacuum support for Hash Index
Previous Message Kuntal Ghosh 2017-03-15 12:14:37 Re: exposing wait events for non-backends (was: Tracking wait event for latches)