Joe Conway confirmed this problem and said that it seems
that the function definition is rewritten to return
1042 (==bpchar), instead of type 18 (==char).
The workaround is to change the SQL definition to have
the function return "char" instead of char (no quotes).
I think it is still a bug,
elein <[EMAIL PROTECTED]> writes:
> I think it is still a bug,
Not unless you can define an upward-compatible migration path to some
non-spec-conflicting typename (I'd favor char1, if we were going to
rename the type).
regards, tom lane
---(end of
