From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
---|---|
To: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> |
Cc: | Jesper Pedersen <jesper(dot)pedersen(at)redhat(dot)com>, Rajkumar Raghuwanshi <rajkumar(dot)raghuwanshi(at)enterprisedb(dot)com>, Beena Emerson <memissemerson(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, Robert Haas <robertmhaas(at)gmail(dot)com>, amul sul <sulamul(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
Subject: | Re: [HACKERS] Runtime Partition Pruning |
Date: | 2018-02-23 12:04:48 |
Message-ID: | CANP8+jL9oSd6zrVmKy5KBQMkR1FZnSZtm3DDSNkdVwPvh8=CdA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 23 February 2018 at 11:40, David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> wrote:
> On 23 February 2018 at 04:11, Jesper Pedersen
> <jesper(dot)pedersen(at)redhat(dot)com> wrote:
>> Are UPDATE and DELETE suppose to be supported ?
>
> To be honest, I had not even considered those.
I can say that I had considered those. Handling of UPDATE and DELETE
with partitions is significantly different, so its not just an
oversight its a different branch of the project.
We need SELECT to work first and then we have a chance of making
UPDATE/DELETE work.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2018-02-23 13:15:07 | Re: FOR EACH ROW triggers on partitioned tables |
Previous Message | David Rowley | 2018-02-23 11:40:13 | Re: [HACKERS] Runtime Partition Pruning |