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+clcnto24youugtsq4zrpheb8euupjdxzjnl4n4...@mail.gmail.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(-) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
