On Sun, May 13, 2012 at 8:11 PM, Tom Lane
<tgl@sss.pgh.pa.us> wrote:
It strikes me that "cannot be cast" is a poor choice of words here,
since the types *can* be cast if you try. Would it be better if the
message said "cannot be cast implicitly to type foo"? We could also
consider a HINT mentioning use of USING.
Without the hint, I don't think that there's a ton of value in changing the message as proposed. It's more accurate, so may be worth doing anyway, but probably won't be much more helpful than the current message to someone who hasn't encountered the problem before. If they've seen it before, the old message is likely sufficient to remind them.