> +lmerge_matched: > ... > + foreach(l, resultRelInfo->ri_matchedMergeAction) > > I suggest expanding the foreach macro into the form of for loop where the > loop condition has extra boolean variable merge_matched. > Initial value for merge_matched can be true. > Inside the loop, we can adjust merge_matched's value to control whether the > for loop continues. > This would avoid using goto label.
Heh, have you seen the definition of foreach() lately? I do *not* want to expand that anywhere. Anyway, even if we had the old foreach() (before commit 1cff1b95ab6d), ISTM that the goto makes the whole thing much clearer. For example, where would you do the table_tuple_fetch_row_version call that currently lies after the goto label but before the foreach loop starts?
The table_tuple_fetch_row_version() can be called before the next iteration starts (followed by the adjustment of loop control variables).
Since you feel using goto is clearer, it is Okay to keep the current formulation.