| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: On partitioning |
| Date: | 2014-10-28 12:19:36 |
| Message-ID: | CA+TgmoaHPXfStSk2QERkWkWPnc63HRDgn=+9Nwt+HTd-=dUv+Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Oct 28, 2014 at 6:06 AM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> In my opinion we can reuse (some of) the existing logic for INHERITS to
> implement "proper" partitioning, but that should be an implementation
> detail.
Sure, that would be a sensible way to do it. I mostly care about not
throwing out all the work that's been done on the planner and
executor. Maybe you're thinking we'll eventually replace that with
something better, which is fine, but I wouldn't underestimate the
effort to make that happen. For example, I think it's be sensible for
the first patch to just add some new user-visible syntax with some
additional catalog representation that doesn't actually do all that
much yet. Then subsequent patches could use that additional metadata
to optimize partition prune, implement tuple routing, etc.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2014-10-28 12:20:06 | Re: Trailing comma support in SELECT statements |
| Previous Message | Fujii Masao | 2014-10-28 12:07:25 | Re: BUG: *FF WALs under 9.2 (WAS: .ready files appearing on slaves) |