Ken Johanson <pg-user@kensystem.com> writes:
>>> What is wrong with using VARCHAR for your
>>> purpose????????????????????????????
> Simply that a commonly used database (my) does not support it.
They do support char(n) in this context, which would have the advantage
of being standards compliant as well as de-facto portable.
> Even at the expense of its standards deviation, and for doubting the
> vendor(s) will the change behavior (and break the app).
You say that with a straight face while arguing for us to diverge from
the spec? It seems unlikely to me that other DBs would change their
historical behavior except to make it comply to spec.
regards, tom lane