On Jan 19, 2012, at 4:27 PM, Robert Haas wrote:
> I think the real fix for this problem is to introduce an
> infrastructure inside the database that allows us to have different
> columns stored in different encodings. People use bytea for that
> right now, but that's pretty unfriendly: it would be nice to have a
> better system. However, I expect that to take a lot of work and break
> a lot of things, and until we do it I don't feel that compelled to
> provide buggy and incomplete support for it under the guise of
> implementing a JSON datatype.
+1 This seems like a reasonable compromise and course of action, especially if someone is interested in taking on
column-levelencodings at some point in the next year or two.
Best,
David