wieck(at)debis(dot)com (Jan Wieck) writes:
>> Net result for user-defined-datatype authors will be "if you revise
>> your routines, they will be easier to read, more portable, and will
>> support TOASTed values. If you don't, they'll still work about as
>> well (or poorly) as they did before."
> Sorry, but that ain't true. Making an existing type toastable
> means that all functions, receiving that type need to be
> revised.
What I meant was that they'd still work, with a limit on field size,
just like before. ie, no TOAST support.
regards, tom lane