On Wednesday 29 July 2009 20:16:48 decibel wrote: > bytea doesn't cast well to and from text when you're dealing with hex > data; you end up using the same amount of space as a varchar. What > would probably work well is a hex datatype that internally works like > bytea but requires that the input data is hex (I know you can use > encode/decode, but that added step is a pain). A similar argument > could be made for base64 encoded data.
There is a patch in the queue that adds hex input and output to bytea. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
