mirror of
https://github.com/postgres/postgres.git
synced 2025-05-03 22:24:49 +03:00
Repair oversight in creation of "append relations": we should set up
rel->tuples as well as rel->rows, since some estimation functions expect both to be valid in every baserel. Per report from Dave Dutcher.
This commit is contained in:
parent
8a114e0031
commit
01d9754bd9
@ -8,7 +8,7 @@
|
||||
*
|
||||
*
|
||||
* IDENTIFICATION
|
||||
* $PostgreSQL: pgsql/src/backend/optimizer/path/allpaths.c,v 1.154 2006/10/04 00:29:53 momjian Exp $
|
||||
* $PostgreSQL: pgsql/src/backend/optimizer/path/allpaths.c,v 1.154.2.1 2007/01/28 18:50:48 tgl Exp $
|
||||
*
|
||||
*-------------------------------------------------------------------------
|
||||
*/
|
||||
@ -383,6 +383,12 @@ set_append_rel_pathlist(PlannerInfo *root, RelOptInfo *rel,
|
||||
}
|
||||
}
|
||||
|
||||
/*
|
||||
* Set "raw tuples" count equal to "rows" for the appendrel; needed
|
||||
* because some places assume rel->tuples is valid for any baserel.
|
||||
*/
|
||||
rel->tuples = rel->rows;
|
||||
|
||||
/*
|
||||
* Finally, build Append path and install it as the only access path for
|
||||
* the parent rel. (Note: this is correct even if we have zero or one
|
||||
|
Loading…
x
Reference in New Issue
Block a user