elein <elein(at)sbcglobal(dot)net> writes:> I think it is still a bug,
Not unless you can define an upward-compatible migration path to somenon-spec-conflicting typename (I'd favor char1, if we were going torename the type).
regards, tom lane