DELETE / UPDATE from partition not optimized (11.0)

If SELECT is confident enough to limit itself to one partition, why isn't DELETE (or UPDATE)? Also, I note in the query plan shown below it thinks the rows in the irrelevant partitions is something other than 0, which is impossible. (presumably, SELECT correctly determined this, and eliminated the

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

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, pruni

Re: Gained %20 performance after disabling bitmapscan

On Mon, Oct 22, 2018 at 3:20 AM Yavuz Selim Sertoglu < [email protected]> wrote: > Thanks for the reply Jeff, > > I know 20ms is nothing but it shows me that there is a problem with my > configuration. I want to find it. > This is a dangerous assumption. This is no configurati