Re: [HACKERS] Runtime Partition Pruning - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: [HACKERS] Runtime Partition Pruning
Date
Msg-id CANP8+jL9oSd6zrVmKy5KBQMkR1FZnSZtm3DDSNkdVwPvh8=CdA@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Runtime Partition Pruning  (David Rowley <david.rowley@2ndquadrant.com>)
Responses Re: [HACKERS] Runtime Partition Pruning  (Amit Langote <amitlangote09@gmail.com>)
List pgsql-hackers
On 23 February 2018 at 11:40, David Rowley <david.rowley@2ndquadrant.com> wrote:
> On 23 February 2018 at 04:11, Jesper Pedersen
> <jesper.pedersen@redhat.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


pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: [HACKERS] Runtime Partition Pruning
Next
From: Alvaro Herrera
Date:
Subject: Re: FOR EACH ROW triggers on partitioned tables