| From: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
|---|---|
| To: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Tweak cost_merge_append to reflect 7a2fe9bd? |
| Date: | 2016-11-04 21:05:22 |
| Message-ID: | CAEepm=0WQBSvuYcMOUj4Ga4NXpu2J=ejZcE=e=eiTjTX-6_gDw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi
As noted in a nearby review of some similar code[1], commit 7a2fe9bd
made merge append very slightly more efficient, but nobody told
cost_merge_append about the change. I doubt it makes much difference
to the final cost in practice but I figured it might be worth
correcting the comment. Does this make sense?
--
Thomas Munro
http://www.enterprisedb.com
| Attachment | Content-Type | Size |
|---|---|---|
| tweak-merge-append-costing.patch | application/octet-stream | 1.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-11-04 21:28:09 | Re: Fix bug in handling of dropped columns in pltcl triggers |
| Previous Message | Tom Lane | 2016-11-04 20:46:44 | Re: Calculation of param_source_rels in add_paths_to_joinrel |