"David E. Wheeler" <david@kineticode.com> writes:
> On Jun 30, 2009, at 11:18 AM, Tom Lane wrote:
>> What's the argument
>> for needing to handle this differently from DATATYPE_MISMATCH?
> For my results_eq() in pgTAP, it could output different diagnostics.
Well, that's not terribly compelling ;-). I wouldn't have any big
objection to splitting out ERRCODE_COLUMN_COUNT_MISMATCH as a separate
SQLSTATE for 8.5 and beyond, but I doubt we'd consider back-patching
such a change. It's not clear to me whether you need a solution that
works in back branches.
regards, tom lane