Re: Possible fault with resolve column name (plpgsql)

Ranier Vilela <ranier.vf@gmail.com> writes:
> Found by llvm scan build.
> Argument with 'nonnull' attribute passed null pl/plpgsql/src/pl_comp.c
> resolve_column_ref

This is somewhere between pointless and counterproductive.

  colname won't
be used unless the switch has set nnames_field (and the identified number
of names matches that). 

If that logic somehow went wrong, I'd *want*
the later strcmp to dump core, not possibly give a false match.