aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeModifyTable.c
diff options
context:
space:
mode:
authorTomas Vondra <tomas.vondra@postgresql.org>2020-11-03 20:07:23 +0100
committerTomas Vondra <tomas.vondra@postgresql.org>2020-11-03 22:32:34 +0100
commit2d26c4ac703447a002a02124c1edd01e70a5d1ee (patch)
treeeadbb37000a13cca7882537af987c5b23ffc37e6 /src/backend/executor/nodeModifyTable.c
parent936043c9eacb9e9c7356a8190a410d2c4e4ea03a (diff)
downloadpostgresql-2d26c4ac703447a002a02124c1edd01e70a5d1ee.tar.gz
postgresql-2d26c4ac703447a002a02124c1edd01e70a5d1ee.zip
Fix get_useful_pathkeys_for_relation for volatile expressions
When considering Incremental Sort below a Gather Merge, we need to be a bit more careful when matching pathkeys to EC members. It's not enough to find a member whose Vars are all in the current relation's target; volatile expressions in particular need to be contained in the target, otherwise it's too early to use the pathkey. Reported-by: Jaime Casanova Author: James Coleman Reviewed-by: Tomas Vondra Backpatch-through: 13, where the incremental sort code was added Discussion: https://postgr.es/m/CAJGNTeNaxpXgBVcRhJX%2B2vSbq%2BF2kJqGBcvompmpvXb7pq%2BoFA%40mail.gmail.com
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions