summaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistproc.c
diff options
context:
space:
mode:
authorAlvaro Herrera <alvherre@alvh.no-ip.org>2018-08-16 12:43:04 -0300
committerAlvaro Herrera <alvherre@alvh.no-ip.org>2018-08-16 12:53:43 -0300
commit1eb9221585c25cad1a563bc3414f697dae3fbc8b (patch)
treea50d44ced642627e8c8c936c254d88acab732157 /src/backend/access/gist/gistproc.c
parentfa73b377ee11ced0c051fb42c29a87b5c71b79e3 (diff)
downloadpostgresql-1eb9221585c25cad1a563bc3414f697dae3fbc8b.tar.gz
Fix executor prune failure when plan already pruned
In a multi-layer partitioning setup, if at plan time all the sub-partitions are pruned but the intermediate one remains, the executor later throws a spurious error that there's nothing to prune. That is correct, but there's no reason to throw an error. Therefore, don't. Reported-by: Andreas Seltenreich <seltenreich@gmx.de> Author: David Rowley <david.rowley@2ndquadrant.com> Discussion: https://postgr.es/m/87in4h98i0.fsf@ansel.ydns.eu
Diffstat (limited to 'src/backend/access/gist/gistproc.c')
0 files changed, 0 insertions, 0 deletions