Re: Problem with default partition pruning

Simon Riggs <simon@2ndquadrant.com>

From: Simon Riggs <simon@2ndquadrant.com>

To: Alvaro Herrera <alvherre@2ndquadrant.com>

Cc: Amit Langote <amitlangote09@gmail.com>, Kyotaro Horiguchi <horikyota.ntt@gmail.com>, yuzuko <yuzukohosoya@gmail.com>, shawn wang <shawn.wang.pg@gmail.com>, Shawn Wang <shawn.wang@highgo.ca>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2019-08-12T17:49:31Z

Lists: pgsql-hackers

On Mon, 12 Aug 2019 at 18:45, Alvaro Herrera <alvherre@2ndquadrant.com>
wrote:

> I think that should appease
> Simon's performance concern for the most common case of default
> partition not existing.
>

Much appreciated, thank you.

-- 
Simon Riggs                http://www.2ndQuadrant.com/
<http://www.2ndquadrant.com/>
PostgreSQL Solutions for the Enterprise

Commits

Don't constraint-exclude partitioned tables as much
- 815ef2f568c7 13.0 landed
Apply constraint exclusion more generally in partitioning
- 4e85642d935e 13.0 landed
Improve pruning of a default partition
- e3967a16d3a0 11.5 landed
- 86544071484a 12.0 landed
- 489247b0e615 13.0 landed
Doc: Fix event trigger firing table
- 44460d7017cd 13.0 cited
Remove obsolete nbtree insertion comment.
- 489e431ba56b 12.0 cited