mirror of
https://github.com/postgres/postgres.git
synced 2026-04-15 22:10:45 -04:00
is using mark/restore but not rewind or backward-scan capability. Insert a materialize plan node between a mergejoin and its inner child if the inner child is a sort that is expected to spill to disk. The materialize shields the sort from the need to do mark/restore and thereby allows it to perform its final merge pass on-the-fly; while the materialize itself is normally cheap since it won't spill to disk unless the number of tuples with equal key values exceeds work_mem. Greg Stark, with some kibitzing from Tom Lane. |
||
|---|---|---|
| .. | ||
| logtape.c | ||
| Makefile | ||
| tuplesort.c | ||
| tuplestore.c | ||