| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Necati Batur <necatibatur(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: GSOC PostgreSQL partitioning issue |
| Date: | 2010-04-08 20:18:00 |
| Message-ID: | y2o603c8f071004081318z4501114ela9d7dbca1a8fa763@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Apr 8, 2010 at 4:14 PM, Necati Batur <necatibatur(at)gmail(dot)com> wrote:
> The more specific of the items will just be the exact job I guess.
> However the detailed form will be hard to write now.
> Or should I explain the sql issues for each point?
Partitioning is a big project. It seems to me that if you want to
have any chance of making a meaningful contribution in one summer,
you're going to need to have a pretty specific idea of what you hope
to accomplish up front, and I don't think you have that right now.
The hard changes are not going to be adjustments to SQL syntax, but in
the guts of the planner, executor, system catalogs, etc.
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Necati Batur | 2010-04-08 20:23:54 | Re: GSOC PostgreSQL partitioning issue |
| Previous Message | Necati Batur | 2010-04-08 20:14:32 | Re: GSOC PostgreSQL partitioning issue |