aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeModifyTable.c
diff options
context:
space:
mode:
authorTomas Vondra <tomas.vondra@postgresql.org>2020-12-15 23:13:38 +0100
committerTomas Vondra <tomas.vondra@postgresql.org>2020-12-15 23:19:41 +0100
commit6bc27698324a3eadb8a4a5a79d96e16687be6141 (patch)
tree6f30c03d872d8fbc10419bec1f206792c7581be9 /src/backend/executor/nodeModifyTable.c
parentc06d6aa4c35177655e0fd4acaca888a73c3f9845 (diff)
downloadpostgresql-6bc27698324a3eadb8a4a5a79d96e16687be6141.tar.gz
postgresql-6bc27698324a3eadb8a4a5a79d96e16687be6141.zip
Error out when Gather Merge input is not sorted
To build Gather Merge path, the input needs to be sufficiently sorted. Ensuring this is the responsibility of the code constructing the paths, but create_gather_merge_plan tried to handle unsorted paths by adding an explicit Sort. In light of the recent issues related to Incremental Sort, this is rather fragile. Some of the expressions may be volatile or parallel unsafe, in which case we can't add the Sort here. We could do more checks and add the Sort in at least some cases, but it seems cleaner to just error out and make it clear this is a bug in code constructing those paths. Author: James Coleman Reviewed-by: Tomas Vondra Discussion: https://postgr.es/m/CAAaqYe8cK3g5CfLC4w7bs%3DhC0mSksZC%3DH5M8LSchj5e5OxpTAg%40mail.gmail.com 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