diff options
| author | Andrew Gierth <rhodiumtoad@postgresql.org> | 2020-11-24 20:58:32 +0000 |
|---|---|---|
| committer | Andrew Gierth <rhodiumtoad@postgresql.org> | 2020-11-24 21:18:37 +0000 |
| commit | 018e7d98dc157265efc4121e2b5971c0a2afcbe1 (patch) | |
| tree | a22352382fbe36408507bf7cc7b3cd010181d9d9 /src/backend/parser/parse_collate.c | |
| parent | 57b5d8484c8a0949c3fa8205a324ac7bf3a377fb (diff) | |
| download | postgresql-018e7d98dc157265efc4121e2b5971c0a2afcbe1.tar.gz postgresql-018e7d98dc157265efc4121e2b5971c0a2afcbe1.zip | |
Properly check index mark/restore in ExecSupportsMarkRestore.
Previously this code assumed that all IndexScan nodes supported
mark/restore, which is not true since it depends on optional index AM
support functions. This could lead to errors about missing support
functions in rare edge cases of mergejoins with no sort keys, where an
unordered non-btree index scan was placed on the inner path without a
protecting Materialize node. (Normally, the fact that merge join
requires ordered input would avoid this error.)
Backpatch all the way since this bug is ancient.
Per report from Eugen Konkov on irc.
Discussion: https://postgr.es/m/87o8jn50be.fsf@news-spur.riddles.org.uk
Diffstat (limited to 'src/backend/parser/parse_collate.c')
0 files changed, 0 insertions, 0 deletions