Nikhil Benesch <nikhil.benesch@gmail.com> writes:
> I could find only a tiny smattering of examples where format_type_be()
> is invoked with a constant OID. In almost all error messages where the
> type is statically known, it seems the type name is hardcoded into the
> error message rather than generated via format_type_be(). For example,
> all of the "TYPE out of range" errors.
Yeah, but we've been slowly converting to that method to reduce the number
of distinct translatable strings for error messages. If doing so here
would cut the labor for translators, I'm for it.
regards, tom lane