| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql: Fix latent costing error in create_merge_append_path. |
| Date: | 2016-11-19 20:06:48 |
| Message-ID: | E1c8BuS-0003AV-FX@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Fix latent costing error in create_merge_append_path.
create_merge_append_path should use the path rowcount it just computed,
not rel->tuples, for costing purposes. Those numbers should always be
the same at present, but if we ever support parameterized MergeAppend
paths (a case this function is otherwise prepared for), the former would
be right and the latter wrong.
No need for back-patch since the problem is only latent.
Ashutosh Bapat
Discussion: <CAFjFpRek+cLCnTo24youuGtsq4zRphEB8EUUPjDxZjnL4n4HYQ(at)mail(dot)gmail(dot)com>
Branch
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/0832f2db68cc43524a240db47d0428cc9525723e
Modified Files
--------------
src/backend/optimizer/util/pathnode.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-11-20 19:26:46 | pgsql: Prevent multicolumn expansion of "foo.*" in an UPDATE source exp |
| Previous Message | Tom Lane | 2016-11-19 19:26:28 | pgsql: Code review for GUC serialization/deserialization code. |