I'm looking at the updated patch (plpgsql-extra-check-180316.patch), and this time it applies and builds OK. The one thing I noticed is that the documentation still uses the old wording for strict_multi_assignement:
WARNING: Number of evaluated fields does not match expected. HINT: strict_multi_assignement check of extra_warnings is active. WARNING: Number of evaluated fields does not match expected. HINT: strict_multi_assignement check of extra_warnings is active.
This was reworded to "Number of source and target fields in assignment does not match."
fixed
Regards
Pavel
Otherwise it seems fine to me, and I'm tempted to mark it RFC once the docs get fixed. Stephen, any objections?
regards
-- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
