Re: BUG #4939: error query result

Itagaki Takahiro <itagaki.takahiro@oss.ntt.co.jp> writes:
> The result might be a designed behavior, but is very surprising.
> What should we care for it?

I think the only thing we could do about it is downgrade the implicit
casts to "name", which seems like a cure worse than the disease ---
it'd interfere with searches in the system catalogs.

The OP could avoid the problem by declaring "str" as text rather
than char(n), which on the whole seems like the preferable solution.
char(200) has got no redeeming social value whatsoever...

            regards, tom lane