Ron Snyder <snyder@roguewave.com> writes:
> That's all just background for my real question-- is there anything in the
> standards (or elsewhere) that says you can't put binary(**) data into a char
> field? When I changed the field to a bytea, processing time was
> significantly reduced.
bytea is the right thing. char will not support null (zero) bytes in
the data, and you may have character-set-encoding issues as well.
regards, tom lane