Re: DELETE / UPDATE from partition not optimized (11.0)

From: Justin Pryzby <pryzby(at)telsasoft(dot)com>
To: Dave E Martin <postgresql2-to(dot)dave(at)dave(dot)to>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: DELETE / UPDATE from partition not optimized (11.0)
Date: 2018-10-26 15:45:40
Message-ID: 20181026154540.GA27004@telsasoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Thu, Oct 25, 2018 at 10:43:10AM -0600, Dave E Martin wrote:
> If SELECT is confident enough to limit itself to one partition, why isn't
> DELETE (or UPDATE)?

Because of this limitation:

https://www.postgresql.org/docs/current/static/ddl-partitioning.html#DDL-PARTITION-PRUNING
|Currently, pruning of partitions during the planning of an UPDATE or DELETE
|command is implemented using the constraint exclusion method (however, it is
|controlled by the enable_partition_pruning rather than constraint_exclusion) —
|see the following section for details and caveats that apply.

Justin

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Jeff Janes 2018-10-26 17:54:32 Re: Gained %20 performance after disabling bitmapscan
Previous Message Dave E Martin 2018-10-25 16:43:10 DELETE / UPDATE from partition not optimized (11.0)