Excerpts from Florian Weimer's message of Thu Nov 24 11:27:51 +0200 2011:
>
> > and why you don't use bytea ? Text should be correct literal.
>
> It's actually UTF-8 text, and some PostgreSQL functions are only
> available for TEXT, but not BYTEA, e.g.:
>
> bfk_int=> SELECT '\x006500'::bytea ~ 'A';
> ERROR: operator does not exist: bytea ~ unknown
And how will those TEXT functions behave on a value with an embedded NUL? Or is it not only about being able to *store* NULs in a text field?
--
Alex