Robert Haas <[email protected]> writes:
> That rearrangement got done in v11, and I've now committed that patch
> after fixing a few typos that I found. Cautiously, woohoo, but let's
> see if anything breaks.
skink's not happy:
=2162940== VALGRINDERROR-BEGIN
==2162940== Conditional jump or move depends on uninitialised value(s)
==2162940== at 0x434D366: cost_material (costsize.c:2593)
==2162940== by 0x436E7E9: materialize_finished_plan (createplan.c:6531)
==2162940== by 0x4383054: standard_planner (planner.c:533)
==2162940== by 0x4383541: planner (planner.c:324)
==2162940== by 0x44C50B4: pg_plan_query (postgres.c:905)
==2162940== by 0x4237444: standard_ExplainOneQuery (explain.c:354)
==2162940== by 0x42375DF: ExplainOneQuery (explain.c:310)
==2162940== by 0x4237A7A: ExplainOneUtility (explain.c:458)
==2162940== by 0x42375C3: ExplainOneQuery (explain.c:301)
==2162940== by 0x4237745: ExplainQuery (explain.c:224)
==2162940== by 0x44CC834: standard_ProcessUtility (utility.c:868)
==2162940== by 0x44CD09D: ProcessUtility (utility.c:525)
==2162940== Uninitialised value was created by a stack allocation
==2162940== at 0x436E76A: materialize_finished_plan (createplan.c:6506)
==2162940==
==2162940== VALGRINDERROR-END
regards, tom lane
