diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2010-09-23 15:34:56 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2010-09-23 15:34:56 -0400 |
| commit | ee63981c1fe26299162b9c7f1218d7e3ef802409 (patch) | |
| tree | e2bac3a19ca08c466d92e9e722fe2e66a9b7261a | |
| parent | 003788e81e7f72bc545b509e1517a672d891273b (diff) | |
| download | postgresql-ee63981c1fe26299162b9c7f1218d7e3ef802409.tar.gz postgresql-ee63981c1fe26299162b9c7f1218d7e3ef802409.zip | |
Avoid sharing subpath list structure when flattening nested AppendRels.
In some situations the original coding led to corrupting the child AppendRel's
subpaths list, effectively adding other members of the parent's list to it.
This was usually masked because we never made any further use of the child's
list, but given the right combination of circumstances, we could do so. The
visible symptom would be a relation getting scanned twice, as in bug #5673
from David Schmitt.
Backpatch to 8.2, which is as far back as the risky coding appears. The
example submitted by David only fails in 8.4 and later, but I'm not convinced
that there aren't any even-more-obscure cases where 8.2 and 8.3 would fail.
| -rw-r--r-- | src/backend/optimizer/path/allpaths.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/optimizer/path/allpaths.c b/src/backend/optimizer/path/allpaths.c index 2d86da3835f..b7cf0b815b7 100644 --- a/src/backend/optimizer/path/allpaths.c +++ b/src/backend/optimizer/path/allpaths.c @@ -425,7 +425,7 @@ set_append_rel_pathlist(PlannerInfo *root, RelOptInfo *rel, childpath = childrel->cheapest_total_path; if (IsA(childpath, AppendPath)) subpaths = list_concat(subpaths, - ((AppendPath *) childpath)->subpaths); + list_copy(((AppendPath *) childpath)->subpaths)); else subpaths = lappend(subpaths, childpath); |