James Robinson <jlrobins@socialserve.com> writes:
> Hmm. Teach me to not send in the exact script / dataset that caused the
> issue. Indeed, I must have (luckily) had a separate syntax error in the
> version that caused the 7.4.6 parser to trip up on the ELSEIF line (it
> did happen else I'd still be staring at the thing).
It occurs to me that one simple thing we could do is make plpgsql accept
both ELSIF and ELSEIF as legal spellings of the keyword. This seems a
bit ugly but I can't think of any really good objections.
regards, tom lane